Skip to main content
Glama

Dilligence — certidões de empresas

Ler documento

read_document
Read-onlyIdempotent

Lê o documento de um item (certidão emitida ou arquivo enviado): texto completo do PDF, resultado, validade e código. include_file=true também anexa o PDF em base64.

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

Input Schema

NameRequiredDescriptionDefault
item_idYes
diligence_idYes
include_fileNo

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?

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds real value beyond that by disclosing the return payload (PDF text, result, validity, code) and the side effect of include_file=true, which attaches a base64 PDF and therefore implies a much larger response. It does not warn about payload size or truncation, which would have pushed it higher.

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 front-loaded sentence with a colon that lists outputs, followed by one short clause on the optional flag. No filler, though the parenthetical about document kinds could be tightened.

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

Completeness4/5

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

There is no output schema, and the description compensates by naming the returned fields, which is the key missing piece for a read tool. Remaining gaps are minor: no behavior described for an item with no document attached, and no note on text truncation for large PDFs.

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 carries the full burden. It meaningfully explains the one non-obvious parameter (include_file=true attaches the PDF in base64), but diligence_id and item_id get no explanation of format or where they come from, leaving two of three parameters undocumented.

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?

States a specific verb and resource ("Lê o documento de um item") and enumerates what the read yields: full PDF text, result, validity and code. It also scopes the resource to two document kinds (issued certificate or uploaded file), which distinguishes it from item-metadata siblings like get_item. It stops short of naming an explicit sibling alternative, so it is clear but not fully differentiated.

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

Usage Guidelines3/5

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

Usage is only implied: the parenthetical narrows the applicable cases to certificates and uploaded files, and the include_file clause hints when to opt in. There is no explicit when-to-use vs when-not guidance and no pointer to alternatives such as get_item, fetch_certidoes or export_documents for other retrieval needs.

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.