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 | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, idempotentHint, and destructiveHint as false. The description adds no extra behavioral details (e.g., rate limits, side effects), but does not contradict the annotations. Since annotations cover the safety profile, the description scores at the neutral baseline.
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, concise sentence that covers all key aspects without redundancy. It is well-structured and free of unnecessary details.
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 tool is simple with no parameters and no output schema provided. The description sufficiently enumerates what the returned state includes, making it complete for an agent to understand the tool's function.
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 the schema coverage is effectively 100%. The description adds no parameter-specific information, but there is nothing to document. Per the rubric, with 0 params the baseline is 4.
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 the current toolkit state, including installed MCPs, connection status, connected accounts, and tool counts. It is specific and distinct from sibling tools like authenticate or connect, which have different purposes.
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 implies usage when one needs an overview of the toolkit's status. It does not explicitly contrast with alternatives, but given the read-only nature and lack of similar info tools (show_version likely targets version only), the context is reasonably clear. Slight deduction for not explicitly stating when to prefer this 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.
As ferramentas têm funções majoritariamente distintas: autenticação, consulta, conexão, marketplace, suporte, versão e estado do toolkit. Há alguma ambiguidade entre connect/authenticate e entre marketplace/toolkit_info, mas as descrições permitem separar os usos.
Os nomes alternam entre verbos simples, verbos com complemento, substantivos compostos e a estrutura híbrida em português `car_demonstrativo_consultar`. Ainda assim, são legíveis e no geral seguem separação por underscore, o que evita caos total.
São 7 ferramentas, mas apenas `car_demonstrativo_consultar` é realmente do domínio Cadastro Ambiental Rural; as demais são utilitárias genéricas da plataforma MCP. O número total é aceitável, mas o conjunto é desbalanceado para um servidor que deveria ser centrado no domínio.
A operação principal de consulta existe e cobre a necessidade imediata de acesso ao demonstrativo. Porém, não há ferramentas complementares para detalhamento, listagem, status ou variações da consulta CAR, e o servidor fica razoavelmente raso para a amplitude do nome 'Cadastro Ambiental Rural'.