Skip to main content
Glama

Dilligence — certidões de empresas

Anexar documento

upload_document

Anexa um arquivo (PDF, PNG, JPG) a um item, por file_url ou content_base64. PDFs de certidão são lidos (resultado, validade, código).

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

Input Schema

NameRequiredDescriptionDefault
item_idYes
file_urlNo
filenameNo
diligence_idYes
content_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and non-idempotent, so the mutation profile is known. The description adds real value by disclosing that certidão PDFs are parsed and yield resultado, validade and código, which is a behavioral effect not present in any structured field. It still omits size limits, duplicate handling, and what happens when parsing fails.

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 compact sentences with the core action and constraints front-loaded and no filler. The parenthetical format list and the parsing note are dense but each earns its place.

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?

For a 5-parameter mutation tool with no output schema, the description covers the operation, accepted formats, the two input channels, and the parsing side effect. Missing size or error-handling detail keeps it short of fully complete.

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 coverage is 0%, so the description must carry the load and it only partly does: it clarifies that file_url and content_base64 are alternative sources (a one-of constraint absent from the schema) and constrains file types. It says nothing about filename, diligence_id, or item_id beyond the bare notion of an target item.

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: attaches a file (PDF, PNG, JPG) to an item, with the two possible input channels. An agent understands the operation immediately, but nothing distinguishes it from the sibling add_document, which could plausibly mean the same thing.

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?

The description implies usage by noting the file_url / content_base64 alternatives and which PDFs get parsed, but it never states when to pick this over add_document, match_documents, or read_document, nor any prerequisite such as the item existing or the diligence being open.

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.