MCP Agent

Use this playbook when the host already works naturally with tools, structured calls, or MCP-like orchestration.

Recommended surface

• First choice: Use MCP Service
• Underlying data references: Market API, Market WebSocket

Use this agent for

• tool-style price reads
• tool-style asset resolution
• tool-style market resolution
• compact OHLCV reads in an agent runtime

Prompt pattern

Use the AgentQL skill through MCP-style tool routing. Start with market.read_price for the requested asset, then widen to market.resolve_market only if price alone is not enough.

Expected behavior

• Use the hosted MCP server URL directly when the host exposes MCP.
• Keep hosted MCP separate from the gateway base URL.
• Return the shortest structured answer that satisfies the user request.

Common mistakes

• Do not point MCP traffic at the gateway base URL.
• Do not rewrite simple tool tasks into raw HTTP or RPC calls unless the host does not support MCP at all.
• Do not expose internal route semantics when the tool abstraction is enough.