Sign in
connection

Report that one MCP tool fired. Fire-and-forget; records which tool and whether it succeeded, nothing else.

Called automatically by @pathmode/mcp-server once per tool invocation, in connected (cloud) mode ONLY — a keyless local-mode server makes no network request at all. Emits exactly one event, mcp_tool_called, carrying the tool name and outcome; deliberately touches NO api_keys column, so a tool firing never moves last_used_at and the activation series stays comparable across the day this shipped. Accepts only tool and outcome; both are normalised against fixed sets before anything is recorded. Clients must treat failures, including 429, as non-fatal.

post/api/v1/connection/tool-call

Request body

toolstring required

Name of the tool that ran, e.g. check_intent_readiness. Checked against the server's registered tool list; an unrecognised name is recorded as "unknown" rather than stored as given, so this field cannot carry spec content, paths, or anything else from the caller's repo.

outcomestring required

"ok" or "error". Anything else is recorded as "unknown".

Response

OK — invocation recorded

object required

Changes