Skip to main content
Glama

Dilligence — certidões de empresas

Buscar certidões nos órgãos

fetch_certidoes

Pede aos órgãos as certidões da diligência que ainda não foram pedidas (status "ready"), ou só item_ids (também repete as que pararam). Gasta créditos quando a certidão sai: confirme com o usuário se ele não pediu para buscar. Para repetir um item que falhou, retry_item.

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>"
    },
    "name": "fetch_certidoes"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idsNo
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, it discloses that credits are spent when a certificate is issued, that the user should confirm unless they explicitly asked to fetch, and that stopped items may be repeated. These are meaningful behavioral details for an open-world, non-idempotent operation. It does not describe return behavior or async processing, but the annotations already cover the safety profile.

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

Conciseness3/5

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

The description is short and front-loads the main action, but the first sentence is compressed and ambiguous: "ou só item_ids (também repete as que pararam)" is hard to parse. It contains no filler, but clarity could be improved with better sentence structure.

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?

It covers the critical cost and confirmation behavior plus the retry alternative, which is valuable for this non-idempotent, credit-spending tool. However, with no output schema it says nothing about what is returned or whether the request is asynchronous, and it does not address the overlap with request_documents.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It clarifies that item_ids can target specific items and that omitting them requests all eligible certificates for the diligence, but it does not explain the item_ids format, behavior for an empty array, or the exact scope of diligence_id beyond its obvious name.

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 states a specific verb and resource: requesting certificates from agencies for a diligence, limited to certificates not yet requested (status "ready") or to given item_ids. It also explicitly distinguishes the failed-item retry case from retry_item. It does not differentiate from the sibling request_documents, which likely overlaps, so it falls short of full sibling differentiation.

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

Usage Guidelines4/5

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

It gives clear usage context: use it for certificates still in "ready" status, optionally restrict to item_ids, and use retry_item for items that failed. It adds a confirmation guideline tied to credit spending. It does not clarify when to prefer this over request_documents or what prerequisites are required.

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.