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?
The description clarifies that calling with no args returns a link and calling with a token authenticates. It does not contradict annotations (idempotentHint=true, destructiveHint=false) and provides context about the login process.
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 but provides necessary step-by-step guidance. It is structured with conditional instructions, which aids clarity without being overly long.
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?
The description covers the entire authentication process from obtaining a login link to using the token, including an alternative permanent configuration. It does not detail output, but that is acceptable since no output schema is provided.
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?
The only parameter, 'token', is clearly explained: it is the access token to paste for session login. The description also clarifies that it is optional (no args to get the link). This fully covers the schema.
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 indicates that the tool is for authentication, distinct from sibling tools like 'connect' and 'show_version'. It explains the login flow but could be more direct about the primary purpose.
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 explains how to use the tool: call with no args to get a login link, then call with a token. It also suggests a permanent configuration method, but does not explicitly contrast with alternatives or specify when to use it over others.
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 JUCESP document tool is clearly distinct, and most platform tools have unique purposes, but the `marketplace` mega-tool overlaps with several others (connect, toolkit_info, report_bug) and makes boundaries fuzzy. An agent could be confused about whether to call `marketplace` or the more specific standalone tools for the same underlying actions.
Tool names mix English imperative verbs (`authenticate`, `connect`, `report_bug`, `show_version`), nouns (`marketplace`, `toolkit_info`), and a Portuguese snake_case domain tool (`jucesp_documento_consultar`). There is no consistent verb_noun or action_resource pattern across the set.
Seven tools is not inherently excessive, but six of them are generic MCP.AI platform/infrastructure tools unrelated to the server's stated JUCESP document-download purpose. The set is over-scoped for what should be a focused single-domain server, with only one tool actually performing the domain operation.
For the narrow stated purpose of downloading a JUCESP document from NIRE/registration number, `jucesp_documento_consultar` covers the core workflow directly. The main gap is the lack of any lookup/search tool for documents when the user does not already know the required identifiers, but that is a minor workaround gap for this specific domain.