Skip to main content
Glama

Dilligence — certidões de empresas

Ver diligência

get_diligence
Read-onlyIdempotent

Situação de cada item (status, responsável, resultado, validade, código, resumo), links de envio e de leitura, e app_url.

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": {
      "id": "<id>"
    },
    "name": "get_diligence"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds genuine value by enumerating the response payload (per-item fields, submission/read links, app_url) in the absence of an output schema, but says nothing about invalid ids, permissions, or partial data.

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 compact sentence with no padding, front-loaded with the return content. The long parenthetical list is dense but efficient; the only weakness is that it is a noun phrase rather than an action statement.

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 one-parameter read tool with complete annotations and no output schema, describing the returned fields is the right focus and largely covers the output side. However, the input side is left entirely unexplained, so an agent knows what comes back but not exactly what to pass in.

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 the single required parameter 'id' is never explained — the description does not clarify whether it is a diligence id or an item id, nor its format. This is the one ambiguity an agent most needs resolved before calling the tool.

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

Purpose3/5

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

The description enumerates the data returned (per-item status, responsible, result, validity, code, summary, links, app_url) but never states a verb or resource for the action itself — it reads as a return-value spec rather than 'retrieves a diligence by id'. No differentiation from siblings such as get_item or list_diligences is offered.

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 when-to-use guidance, no prerequisites, and no mention of alternatives like get_item (single item) or list_diligences (collection). The agent must infer from the name alone when this tool is appropriate versus its siblings.

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.