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?
Annotations already mark idempotentHint=true and destructiveHint=false. The description adds context about the link generation and session-only vs. permanent connection, without contradicting annotations. It does not detail error handling or output, but annotations reduce the burden.
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 three sentences, front-loaded with the target audience and purpose. It efficiently covers two usage modes without unnecessary detail, though it could be slightly more structured with bullet points.
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?
Despite lacking output schema, the description covers essential behavior for a simple authentication tool: how to obtain a token, two usage paths, and the difference between permanent and session login. It could mention error cases, but the core usage is well-specified.
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 0%, so the description must compensate. It explains that the 'token' parameter is optional: passing it sets a session token, omitting it returns a login link. This adds significant meaning beyond the schema's empty description.
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 authenticates IDE agents (Cursor, etc.), explaining two distinct methods: permanent via config header or session via token argument. It is a specific verb-resource combination that stands out from sibling tools like 'connect' or 'marketplace'.
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 explicit guidance on when to use each method: 'Best: add it to this server's config... Or paste it here for a session-only login.' It also explains calling with no args to get the link, but does not explicitly exclude alternative tools, though no alternative is needed.
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.
Tools are mostly distinct: platform utilities (authenticate, connect, marketplace) have clear separate roles, and microvix_* tools each target a different entity (clientes, lojas, movimento, pedidos, produtos variants, etc.). However, the marketplace tool has multiple sub-functions (search, describe, invoke, install) that could blur boundaries, but its description is thorough enough to prevent confusion.
All tools use consistent snake_case naming. Platform tools are short descriptive words (authenticate, connect, marketplace), while domain-specific tools all follow the 'microvix_entity' pattern (e.g., microvix_clientes_fornec, microvix_produtos). No mixing of conventions or inconsistent verb styles.
With 16 tools, the server is slightly above the ideal range (3-15) but still well-scoped. The platform utilities (6 tools) are necessary for authentication, marketplace interaction, and status; the 10 microvix-* tools cover the core domain tables without bloating. The count is reasonable for a server that combines platform and data query capabilities.
The microvix domain tools provide comprehensive read access to key entities (clientes, lojas, movimento, pedidos, produtos, inventário, vendedores), but there are no write/update tools (e.g., create_cliente, update_produto). For a data query server this may be acceptable, but the absence of CRUD operations is a notable gap if the purpose is to manage Microvix data fully.