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 |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond annotations (idempotentHint=true, readOnlyHint=false), the description explains the two possible behaviors: adding a permanent header to config or using a session-only token. It also clarifies that calling with no args returns a link. This adds useful context about side effects and modes of operation.
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?
The description is somewhat verbose and run-on, with a confusing opening 'MCP.AI for IDE agents' that does not add clear value. However, each subsequent clause carries useful information, and the overall length is manageable.
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 optional-token authentication tool with no output schema, the description covers the essential flow: how to authenticate permanently, how to use a session token, and how to obtain the login link. It lacks explicit mention of return values, but the link is implied in 'get the link'.
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?
With schema coverage at 0%, the description compensates by explaining the 'token' parameter: it is an optional JWT for session login, while omitting it yields a login link. This gives the agent enough meaning to invoke correctly, though it could explicitly state that 'token' is a string.
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 the tool's function: to authenticate by logging in and obtaining an access token, with a primary audience of IDE agents. The verb 'log in' is specific, and the resource (this server's config) is mentioned. It does not explicitly differentiate from sibling 'connect', but the purpose is evident.
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?
The description provides clear guidance on when to use each mode: permanent config via header vs session-only via token parameter, and when to call with no args to get the login link. It gives concrete scenarios and steps, though it does not mention explicit alternatives or exclusions.
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 tools are mostly distinct in purpose: the certificate consultation tool is clearly separate from authentication, connection status, marketplace, and feedback tools. Minor overlap exists between 'connect' and 'toolkit_info' regarding connection status, but descriptions clarify their roles.
Tool names mix languages (Portuguese and English) and conventions: 'certidao_debitos_pj_consultar' uses Portuguese snake_case with noun_verb order, while others like 'authenticate', 'connect', 'marketplace', and 'report_bug' are English verbs or nouns. There is no consistent verb_noun pattern across the set.
Although 7 tools is within a typical range, most are generic MCP platform utilities (authenticate, connect, marketplace, report_bug, show_version, toolkit_info) that are unrelated to the server's stated purpose of issuing federal debt certificates. The core domain is served by only one tool, making the set feel padded and unfocused.
The primary operation—consulting the joint federal debt certificate via CNPJ—is fully covered by 'certidao_debitos_pj_consultar'. For the narrow stated purpose, no obvious dead-ends exist. Additional supporting operations (e.g., historical queries, certificate validation) could be added but are not essential given the tool's description.