Skip to main content
Glama

Dilligence — certidões de empresas

Ler checklist de documentos

match_documents
Read-onlyIdempotent

Lê uma lista de documentos pedidos (checklist colado, e-mail, planilha ou foto em base64) e diz, para cada um, quais certidões do catálogo atendem (source_ids) ou se é um documento que alguém precisa enviar (source_ids vazio). Use antes de create_diligence ou add_document.

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": "match_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
filenameNo
content_base64NoArquivo (PDF, Excel, Word, CSV, imagem) em vez de text

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/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, closed-world), so the bar is lower. The description still adds real behavioral context by explaining the mapping semantics — each matched item yields catalog source_ids, and an empty source_ids means a document a person must upload. It omits limits such as unsupported formats, file size caps, or OCR failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Two sentences with no filler: the first covers what is accepted and what is returned, the second covers when to call it. Front-loaded and appropriately sized for the tool's simplicity.

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 correctly takes on the burden of explaining return values (per-item source_ids or empty), and it covers the input side adequately. Remaining gaps are edge-case behavior for unsupported files and what happens when nothing matches the catalog.

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 only 33%, with just content_base64 documented in the schema. The description compensates partly by enumerating input modalities (pasted text, e-mail, spreadsheet, base64 photo), which implicitly clarifies the text vs. content_base64 split, but it never mentions the filename parameter or the precedence when both text and content_base64 are supplied.

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?

The description names a specific verb and resource ('Lê uma lista de documentos pedidos') and immediately characterizes accepted inputs (pasted checklist, e-mail, spreadsheet, base64 photo), which distinguishes it from read_document and list_catalog. It also states the output shape per item (source_ids filled vs. empty), so an agent knows exactly what the tool produces.

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 explicit ordering guidance: use before create_diligence or add_document, naming two concrete siblings. There is no when-not guidance or mention of alternatives for already-structured catalog lookups (e.g. list_catalog), but the sequencing intent is unambiguous.

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.