Skip to main content
Glama

Dilligence — certidões de empresas

Ver item

get_item
Read-onlyIdempotent

Detalhe completo de um item: resumo inteiro, motivo de ter parado, protocolo, próxima checagem, taxa, tentativas e histórico.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "diligence_id": "<diligence_id>",
      "item_id": "<item_id>"
    },
    "name": "get_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is fully covered elsewhere. The description's real contribution is enumerating the returned fields, which matters because no output schema exists, but it says nothing about format, size, or failure behavior for missing IDs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence leads immediately with what the tool returns; nothing is padded with vague preamble. The trailing list of returned fields is a bit of a laundry list but each item earns its place given the absent output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with safety covered by annotations and no output schema, listing the returned fields is genuinely useful. The gap is the complete absence of parameter semantics and any statement of error/empty behavior, leaving the agent to rely on self-describing ID names.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters (diligence_id, item_id), and the description gives no syntax, format, or sourcing hints to compensate. The agent only benefits from the parameter names being relatively self-explanatory.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (item) and enumerates the exact detail returned (full summary, stopping reason, protocol, next check, fee, attempts, history), which clearly identifies it as a single-item detail reader. It does not, however, distinguish the tool from siblings like get_diligence or list_catalog, so an agent cannot tell its scope apart from those without external knowledge.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use guidance, no exclusions, and no reference to alternatives such as get_diligence or bulk_items. Usage is only implied by the word 'Detalhe completo' – the agent must infer that this is the single-item retrieval path.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.