Skip to main content
Glama

Dilligence — certidões de empresas

Adicionar empresas à carteira

add_monitor_companies

Põe mais CNPJs numa carteira, com as certidões dela, e já manda o robô buscar.

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": {
      "monitor_id": "<monitor_id>",
      "cnpjs": "<cnpjs>"
    },
    "name": "add_monitor_companies"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjsYes
monitor_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false. The description adds real value beyond them by disclosing two side effects: certificates are pulled in, and a background job ('robô') is kicked off. It does not say what happens with duplicate or invalid CNPJs, whether the fetch is synchronous, or what the caller gets back, which matters for a non-idempotent mutation.

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?

One dense sentence with the action and its side effects front-loaded and no filler. The informal register ('robô', 'carteira') is efficient but slightly imprecise for a technical contract.

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

Completeness3/5

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

For a two-parameter mutation with no output schema, the description covers the action and its side effects but omits the return value (job id, added-company list, or errors) and duplicate handling. That leaves a meaningful gap for an agent that needs to confirm success or chain a follow-up call.

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

Parameters2/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 carry the burden. It names both concepts (CNPJs and the portfolio), but gives no format guidance for CNPJ strings (digits only vs. formatted, single vs. batch limits) and never clarifies that monitor_id is the target portfolio identifier. An agent still has to guess at input shape.

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 states a concrete verb and resource: it adds more CNPJs to a portfolio ('carteira'), includes that portfolio's certificates, and triggers a background fetch. An agent can distinguish this from create_monitor or add_document. The only weakness is the vocabulary mismatch between 'carteira' in the description and 'monitor' in the tool name, which requires a small inference.

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 phrase 'põe mais CNPJs numa carteira' suggests adding to an existing portfolio rather than creating one, which implicitly points away from create_monitor. There is no explicit when-to-use or when-not-to-use statement, no mention of prerequisites such as the monitor already existing, and no named alternative.

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.