Skip to main content
Glama

Dilligence — certidões de empresas

Pedir documentos

create_request

Faz um pedido de documentos. to="robot" pede certidões aos órgãos; to=e-mail (com to_name) pede a uma pessoa por link (e-mail só se o usuário pediu: send=true). Dentro de uma diligência (diligence_id; item_ids reaproveita itens dela) ou avulso (cnpj, sem diligência). certidoes e documents como em create_diligence. Para mandar a uma pessoa itens que já estão numa diligência, request_documents é o atalho.

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": {
      "to": "<to>"
    },
    "name": "create_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes"robot" (pede aos órgãos) ou o e-mail da pessoa
cnpjNo
nameNo
sendNoManda o e-mail (só se o usuário pediu)
messageNo
to_nameNoNome da pessoa
item_idsNo
certidoesNo
documentsNo
diligence_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / send
      Added value: +{
      +  "description": "Manda o e-mail (só se o usuário pediu)",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / to / description
      Previous value: -"\"robot\" ou {name, email, send}"New value: +"\"robot\" (pede aos órgãos) ou o e-mail da pessoa"
    • addedInput schema / properties / to / type
      Added value: +"string"
    • addedInput schema / properties / to_name
      Added value: +{
      +  "description": "Nome da pessoa",
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • removedInput schema / properties / send
      Removed value: -{
      -  "description": "Manda o e-mail (só se o usuário pediu)",
      -  "type": "boolean"
      -}
    • changedInput schema / properties / to / description
      Previous value: -"\"robot\" (pede aos órgãos) ou o e-mail da pessoa"New value: +"\"robot\" ou {name, email, send}"
    • removedInput schema / properties / to / type
      Removed value: -"string"
    • removedInput schema / properties / to_name
      Removed value: -{
      -  "description": "Nome da pessoa",
      -  "type": "string"
      -}
  3. Changed4 schema fields changed
    • addedInput schema / properties / send
      Added value: +{
      +  "description": "Manda o e-mail (só se o usuário pediu)",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / to / description
      Previous value: -"\"robot\" ou {name, email, send}"New value: +"\"robot\" (pede aos órgãos) ou o e-mail da pessoa"
    • addedInput schema / properties / to / type
      Added value: +"string"
    • addedInput schema / properties / to_name
      Added value: +{
      +  "description": "Nome da pessoa",
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already signal a mutating, non-idempotent, open-world operation, and the description adds meaningful context on top: requests reach external agencies or a real person, and e-mail delivery is gated behind send=true with an explicit "only if the user asked" guardrail. It does not cover what happens on failure, whether credits are consumed, or what identifier comes back, which keeps it short of a 5.

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?

It is dense but front-loaded: purpose first, then mode rules, then context rules, then the sibling alternative. The telegraphic fragments ("to=e-mail (com to_name) pede a uma pessoa por link") are efficient rather than bloated, though the parenthetical nesting costs some readability.

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 10-parameter mutating tool with no output schema and low schema coverage, the description covers the decisions an agent must make: which target type, whether to send e-mail, and whether to attach to a diligence. Missing are the return value, whether create_diligence-style validation applies to name/message, and any cost/permission prerequisites hinted at by the buy_credits sibling.

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?

With only 30% schema coverage across 10 parameters, the description carries most of the load and does so for eight of them: to (robot vs. e-mail), to_name, send, cnpj (standalone mode), diligence_id, item_ids (reuse a diligence's items), and certidoes/documents (same shape as in create_diligence). name and message are left undefined, which is the remaining gap.

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?

"Faz um pedido de documentos" gives a specific verb and resource, then immediately splits the tool into its two concrete modes: to="robot" (requests certificates from government agencies) and to=<e-mail> (requests from a person via link). It also names the sibling request_documents and states what makes this tool different, so an agent can distinguish it without opening 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?

Explicit routing rules are given for the two modes, plus a hard condition on side effects ("e-mail só se o usuário pediu: send=true"). It also defines the two operating contexts (inside a diligence via diligence_id/item_ids vs. standalone via cnpj) and points to request_documents as the shortcut when the items already belong to a diligence.

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.