Skip to main content
Glama

Dilligence — certidões de empresas

Adicionar documentos

add_document

Adiciona documentos à lista de uma diligência já aberta, para todas as empresas (ou só party_ids, de get_diligence.parties): certidoes (ids de list_catalog) e documents (títulos livres, ex. contrato social, que alguém envia). Também aceita title para um só documento livre. As certidões esperam fetch_certidoes, ou passe fetch=true.

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

Input Schema

NameRequiredDescriptionDefault
fetchNo
titleNo
certidoesNo
documentsNo
party_idsNo
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare it as a non-read-only, non-idempotent, open-world write, so the description's added value is the open-diligence precondition and the side effect that certidões "esperam fetch_certidoes" unless fetch=true is passed. That is useful behavioral context the annotations do not carry, though the fetch default and duplicate-handling behavior are left unstated.

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 dense paragraph that front-loads the verb and resource before the parameter sourcing guidance, with no filler sentences. Some phrasing is compressed to the point of ambiguity ("As certidões esperam fetch_certidoes"), which costs a little clarity.

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

Completeness5/5

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

For a six-parameter mutation tool with no output schema and zero schema-level documentation, the description covers every parameter's meaning, the state precondition, and the fetch alternative. An agent has enough to call it correctly without opening the schema.

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

Parameters4/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 compensate, and it largely does: certidoes = ids from list_catalog, documents = free-text titles (e.g. contrato social), title = single free document, party_ids = from get_diligence.parties with default of all companies, fetch = trigger fetching instead of waiting for fetch_certidoes. diligence_id is only implied by "diligência já aberta", and fetch's default value is never given.

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 gives a specific verb and resource ("Adiciona documentos à lista de uma diligência já aberta") and splits the payload into two named kinds, certidoes and documents, each with its own value source. It does not explicitly contrast with nearby siblings like upload_document or request_documents, so an agent must infer that this records entries rather than uploading files.

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 states a precondition (the diligência must already be open) and routes parameter sourcing to other tools: party_ids from get_diligence.parties, certidoes ids from list_catalog, and the instruction to use fetch_certidoes or pass fetch=true. It stops short of saying when not to use it instead of upload_document/request_documents.

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.