Skip to main content
Glama

Dilligence — certidões de empresas

Criar carteira de monitoramento

create_monitor

Cria uma carteira de monitoramento: os CNPJs ficam em observação e o robô renova cada certidão antes de vencer, na frequência escolhida (diaria, semanal ou mensal; padrão mensal), e avisa a equipe por e-mail quando uma renovação vem positiva ou não sai. Sem certidoes, entram as 12 de um escritório contábil (federal, FGTS, CNDT, TRT, TRF, protestos, estadual, dívida ativa SP, municipal e TJSP cível, falência e execuções fiscais). 1 crédito por certidão emitida, na primeira busca e em cada renovação; positiva com efeitos de negativa conta como negativa. Confirme a lista e a frequência com o usuário antes.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
cnpjsYes
certidoesNoids de list_catalog
frequencyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false) by disclosing the credit cost model (1 credit per certificate on first search and every renewal), the email notification behavior on positive or failed renewals, the default certificate set, and the 'positive with negative effects counts as negative' rule — all material to whether an agent should invoke it.

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?

Purpose and mechanism are front-loaded, and every clause carries operational weight (defaults, cost, notifications, confirmation step). It is a dense single paragraph that could be broken into bullets, but there is no filler to remove.

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 non-idempotent, credit-consuming creation tool with no output schema, the description covers cost, side effects and defaults, which is what an agent needs before acting. It does not say what the tool returns (presumably the new monitor identifier) or how invalid CNPJs are handled, but those are secondary.

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 25% schema coverage, the description carries most of the burden and does so for three of four parameters: certidões defaults to the 12-item accounting-firm list, frequency options and monthly default are stated, and cnpjs is implicitly explained as the entities placed under observation. The `name` parameter is never mentioned anywhere, leaving one genuine 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?

Opens with a specific verb and resource ('Cria uma carteira de monitoramento') and immediately explains the mechanism: CNPJs go under observation and certificates are auto-renewed before expiry. This lets an agent distinguish it from get_monitor, update_monitor, list_monitors and add_monitor_companies without opening a schema.

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?

Gives concrete operating guidance: default frequency is monthly when unspecified, the 12-certificate accounting-firm set applies when no certidões are supplied, and the agent should confirm list and frequency with the user first. It does not, however, name an alternative tool or state when to prefer add_monitor_companies/update_monitor over creating a new portfolio.

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.