Returns the current toolkit state: installed MCPs, their connection status, the accounts connected to each one, and how many catalog tools each exposes.
| 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 cover readOnly, idempotent, and destructive hints. The description adds specific behavioral context about what the returned state includes (connection status, accounts, catalog counts), which goes beyond the annotations and helps the agent set expectations.
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 a single sentence that efficiently lists the key elements of the returned state without redundancies. It is front-loaded with the action 'Returns' and immediately itemizes the content.
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 zero parameters foster no output schema, the description fully specifies what the tool returns: installed MCPs, connection status, connected accounts, and catalog tool counts. No further detail is needed for a simple read-only state inspection tool.
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 parameterschers, so there are no parameter semantics to clarify. The description completely fulfills the requirement without needing to compensate for missing schema details.
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 verb 'Returns' and the resource 'current toolkit state' with specific details (installed MCPs, connection status, accounts, tool counts). It distinguishes itself from siblings like 'connect' and 'authenticate' by focusing on state inspection.
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 context for when to use the tool (to inspect current toolkit state) and implies its role among siblings (e.g., connect/authenticate for modifications). It lacks explicit exclusions or named alternatives, but the purpose is unambiguous.
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 are clearly separated (report_bug, show_version, toolkit_info), but authenticate and connect overlap around credentials/connection status, and marketplace's invoke capability could be confused with the BCB query tool for running data lookups. The line between 'using the platform' and 'querying BCB data' is not crisp.
Naming conventions are mixed: bare verbs (connect), English verb_noun pairs (report_bug, show_version), nouns (marketplace, toolkit_info), and one Portuguese noun_verb construction (bcb_cotacoes_consultar). There is no consistent pattern across the set.
Seven tools is a reasonable count by number, but six of them are generic platform/utility tools (marketplace, connect, authenticate, etc.) with only one BCB-specific tool. The set is not tightly scoped to the server's stated purpose of BCB quotes.
For the actual BCB domain, only one query tool exists; it may cover basic quote lookups but there is no dedicated tool for enumerating available series, currencies, or historical ranges. The core read path exists, but the domain surface feels thin.