Ask questions about the platform, APIs, smart contracts, and feature usage to receive immediate guidance. No API key needed.
Ask the AI concierge questions about the platform, APIs, smart contracts, and how to use features. No api_key required.
| Name | Required | Description | Default |
|---|---|---|---|
| message | Yes | Question or message for the concierge | |
| agent_id | No | Optional agent UUID for context |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that no API key is required, which is useful auth info. However, lacks details on response format, rate limits, or that it's read-only/non-destructive. Without annotations, more behavioral context would help.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence that is efficient and front-loaded with the verb and purpose. No unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple chat tool with 2 parameters and no output schema, the description covers purpose and auth. Could mention return format, but it's adequate for decision-making.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with both parameters described in the schema. The description adds no extra meaning beyond the schema. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action (ask questions) and the resource (AI concierge), and specifies domains (platform, APIs, smart contracts, features). It distinguishes from sibling tools, which are transactional/financial.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implicitly indicates use for Q&A, but no explicit guidance on when not to use or alternatives. Given sibling tools are action-oriented, it's clear this is for queries, but not stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.