MCP.AI for IDE agents (Cursor, etc.): log in in the browser, copy the access token. Best: add it to this server's config as a header Authorization: Bearer <token> for a permanent, non-expiring connection. Or paste it here for a session-only login: call with { token: "" } after the user pastes, or with no args to get the link.
| Name | Required | Description | Default |
|---|---|---|---|
| token | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate idempotent=true, destructive=false, readOnly=false. Description adds details about token handling and link generation. No contradictions. Could mention rate limits or token validation, but sufficient.
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?
Two sentences, front-loaded with context. First sentence is slightly long but packs useful info. Could be more structured with bullets, but efficient.
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?
Given the tool's simplicity and no output schema, description covers essential scenarios. Lacks error handling or token validation details, but complete enough for an agent to use correctly.
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 has one parameter 'token' with 0% description coverage. Description fully explains its meaning and usage (JWT token from browser login). Compensates perfectly for schema gap.
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?
The description clearly states it handles authentication for MCP.AI IDE agents. It specifies three distinct scenarios (permanent config, session paste, no-args link). It differentiates from siblings implicitly as no sibling is authentication-focused, but does not explicitly contrast with 'connect'.
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?
Explicitly describes three usage modes with context: permanent config, session-only paste, and calling with no args to get a link. Does not explicitly state when not to use, but covers main use cases adequately.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The seven fipe_* tools each target a distinct step in the FIPE data lookup (brands, models, years, price, history, search, reference dates), and their names make their purposes clear. However, connect and toolkit_info both report connection status, and marketplace bundles many sub-operations into one tool, creating minor ambiguity.
FIPE tools follow a consistent fipe_<noun> pattern, but the platform tools (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) use generic verbs/nouns without a shared convention, mixing styles within the same server.
13 tools is within the ideal range for a domain-specific data server; the 7 FIPE tools are well-scoped and the 6 platform utilities are justified for authentication, marketplace access, and system status.
The FIPE data surface is complete: marcas → modelos → anos → preco covers the full drill-down, with buscar, historico, and tabelas_referencia adding search, time series, and date selection. No obvious missing operations for the domain.