Skip to main content
Glama

Dilligence — certidões de empresas

Ver catálogo de certidões

list_catalog
Read-onlyIdempotent

Certidões que buscamos: órgão, validade, taxa do órgão, se é automática. Com cnpj, só as que valem para aquela empresa, com o TRT e o TRF da região dela. Famílias regionais: "trt" (TRT da região de cada empresa, TRT-1 a 24) e "trf" (TRF da região, TRF1 a 6) servem como id em create_diligence; ids regionais (trt15, trf1…) pedem um tribunal específico, ex. TRT-15 para uma filial em Campinas. 1 crédito por certidão emitida; reuso em 24 h e falhas não cobram.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
cnpjNoOpcional: só as certidões que valem para esta empresa (pela sede na Receita)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely non-obvious economics: 1 credit per certificate issued, free reuse within 24 hours, and no charge on failures — which also implicitly reassures that browsing the catalog itself is not the billable action. It does not describe pagination or response shape, but no output schema exists so this is a minor gap.

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?

The text is dense but every clause carries information: catalog fields first, then the cnpj filter, then id-family semantics for create_diligence, then credit rules. It is telegraphic and would benefit from clearer sentence separation, but there is no filler.

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?

With no output schema, the description must indicate what comes back, and it does by listing the exposed attributes of each certificate. It also covers the region-specific id taxonomy needed to use the results downstream. What remains unstated is any ordering, total counts, or error behavior, which is acceptable for a small read-only catalog tool.

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 coverage is 100% and there is only one optional parameter, so the schema already explains cnpj as 'pela sede na Receita'. The description goes further, spelling out that filtering by cnpj also pulls in the TRT and TRF covering that company's region — regional logic the schema does not convey. That is meaningful added semantics beyond the structured field.

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 names the resource (certidões) and enumerates what the catalog exposes: órgão, validade, taxa do órgão e se é automática. It does not open with an explicit verb, relying on the name/title for the 'list' action, and it does not contrast itself with siblings like list_templates or find_company. Still, an agent can tell this is the certificate catalog rather than a diligence or document tool.

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 gives concrete guidance on the optional cnpj filter (only certificates valid for that company's region) and, more valuably, explains that the regional family ids 'trt'/'trf' are what you pass to create_diligence, while specific ids like trt15/trf1 target a single tribunal. It never explicitly says 'call this before create_diligence to obtain ids', so the workflow sequencing is inferred rather than stated.

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.