Skip to main content
Glama

Dilligence — certidões de empresas

Ver modelos de diligência

list_templates
Read-onlyIdempotent

Modelos de diligência prontos (ma: aquisição/M&A, credito, fornecedor, licitacao, imovel), já ajustados à sede de cada CNPJ: TRT e TRF da região de cada empresa (todos os TRTs e TRFs); onde não buscamos (TJ, Sefaz e prefeitura fora de SP, prefeituras fora da capital) o modelo troca a certidão de SP pela local (TJMG, SEFAZ-MG...) como documento que a empresa envia, só para aquela empresa. Devolve cada modelo com os itens (certidão do catálogo ou documento, e para quais cnpjs), o que mudou por local (adjustments) e um modelo sugerido pelo nome da diligência. Use antes de create_diligence com template.

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_templates"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoNome da diligência, para sugerir o modelo
cnpjsNo
peopleNoPessoas físicas: CPF e UF

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / people
      Added value: +{
      +  "description": "Pessoas físicas: CPF e UF",
      +  "items": {
      +    "properties": {
      +      "cpf": {
      +        "type": "string"
      +      },
      +      "uf": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  2. Changed1 schema field changed
    • removedInput schema / properties / people
      Removed value: -{
      -  "description": "Pessoas físicas: CPF e UF",
      -  "items": {
      -    "properties": {
      -      "cpf": {
      -        "type": "string"
      -      },
      -      "uf": {
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
  3. Changed1 schema field changed
    • addedInput schema / properties / people
      Added value: +{
      +  "description": "Pessoas físicas: CPF e UF",
      +  "items": {
      +    "properties": {
      +      "cpf": {
      +        "type": "string"
      +      },
      +      "uf": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  4. Changed1 schema field changed
    • removedInput schema / properties / people
      Removed value: -{
      -  "description": "Pessoas físicas: CPF e UF",
      -  "items": {
      -    "properties": {
      -      "cpf": {
      -        "type": "string"
      -      },
      -      "uf": {
      -        "type": "string"
      -      }
      -    },
      -    "type": "object"
      -  },
      -  "type": "array"
      -}
  5. Changed1 schema field changed
    • addedInput schema / properties / people
      Added value: +{
      +  "description": "Pessoas físicas: CPF e UF",
      +  "items": {
      +    "properties": {
      +      "cpf": {
      +        "type": "string"
      +      },
      +      "uf": {
      +        "type": "string"
      +      }
      +    },
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  6. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial value beyond them: the substitution rule (SP certificate replaced by TJMG/SEFAZ-MG etc. only for that company), the fact that nothing is searched in TJ/Sefaz/prefeitura outside SP, and the shape of the result (items, adjustments, suggested template). It does not cover pagination, cost, or whether templates are user-scoped, which keeps it from 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.

Conciseness3/5

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

Information-dense and front-loaded, with the key purpose in the first clause, but it is a single sprawling paragraph with stacked parentheticals ('(TJ, Sefaz e prefeitura fora de SP, prefeituras fora da capital)') that make it slower to parse than it needs to be. Little is padding, but the structure works against it.

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?

No output schema exists, and the description does its job by describing the return payload (items with catalog certificate or document, adjustments, suggested template). Combined with the workflow pointer to create_diligence, an agent has nearly everything needed; only the cnpjs/people parameter roles remain thin.

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 67% and the schema already documents 'name' (nome da diligência para sugerir o modelo) and the people/CPF+UF items. The description only implies that cnpjs drives which companies get adjusted items and that name drives the suggested template, adding little syntax or format detail beyond the schema; baseline 3 applies.

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?

States a specific verb+resource ('Modelos de diligência prontos') and enumerates the template families it covers (ma/M&A, credito, fornecedor, licitacao, imovel), so an agent knows exactly what this returns versus e.g. list_catalog or list_diligences. The scoping detail about per-CNPJ regional adjustment makes the purpose unambiguous.

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?

Explicitly positions itself in the workflow: 'Use antes de create_diligence com template', naming the sibling and the precondition. It doesn't spell out when NOT to use it (e.g. when drafting a diligence from scratch without a template), so it falls short of full when/when-not guidance.

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.