Skip to main content
Glama

Dilligence — certidões de empresas

Buscar certidão de novo

retry_item

Busca a certidão de novo (item que falhou, parou num muro, ou para renovar). Um item só: para vários use bulk_items com action="retry"; para itens nunca pedidos, fetch_certidoes.

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": "retry_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the agent knows this is a non-idempotent mutating outbound call. The description adds nothing beyond that safety profile: it does not say whether a retry consumes credits (a real concern given the sibling buy_credits), whether prior results are replaced, or what happens to the existing item state. With annotations carrying the baseline, a 3 is fair, but the cost/replacement semantics are a missed opportunity for a non-idempotent mutation.

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?

Two short sentences, front-loaded with the action and back-loaded with the routing rules; nothing is wasted. The only friction is the idiomatic 'parou num muro', which is vivid but less precise than a plain state description for a non-native reader.

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 simple two-parameter tool with no output schema, the routing and trigger coverage is good, but the description leaves the identifiers unexplained and says nothing about whether a retry re-charges credits or overwrites the previous result. Those gaps matter precisely because the tool is non-idempotent.

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% and both parameters are required with no descriptions, so the description carries the full burden — but it only implies singular scope via 'Um item só'. It never explains what diligence_id identifies, how item_id relates to it, or whether an item can exist in multiple diligences, leaving the agent to guess at the primary key semantics.

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

Purpose5/5

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

The description gives a specific verb+resource ('Busca a certidão de novo') and immediately scopes it to a single re-request. It explicitly contrasts itself with two siblings (bulk_items with action="retry", and fetch_certidoes for never-requested items), so an agent can route correctly without opening any schema.

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

Usage Guidelines5/5

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

It enumerates the three triggering conditions (failed, 'parou num muro', or renewal) and then names when NOT to use it, with the exact alternative and even the parameter value for the bulk case. This is the strongest possible when/when-not/alternatives guidance.

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.