Skip to main content
POST
Execute GWI MCP v2beta tool calls

Authorizations

Authorization
string
header
required

Format: Bearer YOUR_TOKEN

Body

application/json

JSON-RPC request for any supported v2beta MCP tool

Discover workflow skill keys and short descriptions. Call at the start of each new GWI analysis and when the user shifts to a different workflow type on a follow-up. Match the user request to returned descriptions. Do not invent keys. Full skill bodies are not included — use get_skills for matching keys only. Do not mention this tool or skill mechanics in user-facing replies.

jsonrpc
enum<string>
required
Available options:
2.0
id
required
Example:

1

method
enum<string>
required
Available options:
tools/call
params
object
required

Response

JSON-RPC response. HTTP 200 means the JSON-RPC call was processed, not that the tool succeeded.

Inspect result.isError if present:

  • true — tool failed; the message is in result.content[0].text, and result._meta.isInternalError may be true for internal or timeout-style failures.

See Tool errors (result.isError) in the overview above for full behavior.

JSON-RPC 2.0 success envelope for MCP tools/call (no top-level error field).

When the tool fails, HTTP status is still typically 200 and this object is returned with result.isError: true. Use that flag rather than HTTP status alone.

jsonrpc
enum<string>
required
Available options:
2.0
id
string
required

Request identifier echoed back

result
object
required

MCP tool result. Inspect isError for tool-level success or failure.

isError: true — the tool failed; content usually has one text item with a human-readable explanation. Typical causes:

  • Invalid arguments (e.g. empty prompt, invalid UUID for insight_id where required).
  • Downstream errors (e.g. resource not found, timeout, cancelled request, or generic internal failure).

_meta.isInternalError — when present and true, the server classified the failure as internal or timeout-style. Omitted or false for most validation and not-found style errors.

This is not the same as a JSON-RPC protocol error: invalid method or malformed requests use the standard JSON-RPC error field instead of a tool result.