Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds meaningful behavioral context: the exact return states ('authenticated:true', empty pending[], connect_url) and the existence of per-install URLs. This goes beyond the structured data and enhances the agent's understanding.
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 two sentences, front-loaded with the primary purpose, and then adds conditional details. Every word contributes value; no redundancy or filler.
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 zero-parameter, read-only status tool, the description fully covers the key behavioral states (connected vs. missing credentials) and return URL semantics. The sibling list and annotations fill in any remaining context, making the description complete for selection and invocation.
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 tool has zero parameters, so schema coverage is trivially complete. The description doesn't need to explain parameters, and the baseline of 4 applies due to the absence of parameters. No additional param info is required.
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 'Returns connection status and URLs', which is a specific verb+resource. It distinguishes itself from the sibling 'authenticate' by focusing on status rather than performing authentication, and it mentions 'authenticated:true' to align with the auth context.
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 conditional behavior based on connection state (all providers connected vs. missing credentials), which implies usage for checking whether authentication is needed. It provides clear context but does not explicitly state 'use this to check before authenticating' or mention exclusions relative to siblings.
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.
Most tools have distinct purposes, but marketplace is a broad meta-tool that overlaps with connect and toolkit_info for managing connections and installations, and authenticate/connect are closely related.
Names mix conventions: verb_noun (report_bug, show_version), noun_only (marketplace, toolkit_info), and a Portuguese snake_case phrase (credito_dossie_consultar). No consistent pattern across the set.
Seven tools is a reasonable number, but only one tool directly serves the credit dossier purpose; the other six are generic platform utilities that seem out of scope for a specialized server.
The credit domain is covered by only a single query operation with no supporting operations (e.g., history, batch, management). The rest of the tools are unrelated, leaving the core domain underdeveloped.