Skip to main content
Glama

Dilligence — certidões de empresas

Gerar link de envio

request_documents

Pede vários itens a uma pessoa de fora (ex. o financeiro da empresa). Devolve o link de envio, sem login, com o passo a passo de cada documento. Só envia e-mail se send_email=true. Use para itens que já existem na diligência; para documentos novos ou pedido avulso por CNPJ, use create_request.

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_ids": "<item_ids>",
      "email": "<email>"
    },
    "name": "request_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
emailYes
item_idsYes
send_emailNo
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare flags (readOnly=false, destructive=false, idempotent=false, openWorld=true); the description adds real behavior: the returned artifact is a no-login submission link, the recipient is an outside party, and e-mail is dispatched only when send_email=true. It does not explain what re-invocation does to an already-issued link, which matters given idempotentHint=false, so it stops short of full disclosure.

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

Conciseness5/5

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

Three short sentences, front-loaded with the action and return value, then the conditional e-mail rule, then the sibling routing. No filler and nothing redundant.

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 mutating, world-facing tool with no output schema, the description covers the deliverable, the audience, the conditional side effect, and the routing decision. The remaining gap is repeat-call behavior, which the non-idempotent annotation hints at but the description never resolves.

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% across five parameters, so the description must carry the meaning. It partially does: item_ids is framed as items already existing in the diligence, and send_email is defined semantically as the e-mail gate. The optional 'name' and the exact role of 'email' (recipient vs. requester) are left undefined in both schema and description.

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

Purpose5/5

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

The description opens with a concrete verb and resource: requesting multiple items from an external person (e.g. the company's finance team), and it states what comes back (a no-login submission link with per-document steps). It also names the sibling it is not (create_request), so an agent can distinguish it without reading any schema.

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

Usage Guidelines5/5

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

Usage rules are explicit and paired with the alternative: use this when the items already exist in the diligence; use create_request for new documents or a standalone request by CNPJ. The negative condition is stated, not inferred.

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.