Skip to main content
Glama

Dilligence — certidões de empresas

Aprovar taxa do órgão

approve_fee

Aprova a taxa do órgão para um item (ex. CETESB R$ 138 = 25 créditos, além do crédito da certidão) e retoma a busca. Gasta créditos: confirme 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": {
      "diligence_id": "<diligence_id>",
      "item_id": "<item_id>"
    },
    "name": "approve_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_idYes
diligence_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations, the description discloses two behaviors the agent could not infer: the call consumes credits (with a concrete price example: CETESB R$ 138 = 25 créditos) and it resumes the search after approval. It still does not say what happens if credits are insufficient or whether approval is reversible, so it stops short of 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.

Conciseness4/5

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

Two sentences, both front-loaded: the action first, then the cost warning. The pricing parenthetical is arguably dense but earns its place because it makes the credit cost concrete. No filler wording.

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 cost/confirmation angle well and mentions the post-action state ('retoma a busca'). It remains incomplete on what the identifiers mean and what the agent gets back after approval, which an agent would need to chain follow-up calls.

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% and both parameters (diligence_id, item_id) are required but completely undefined in the schema. The description only says 'para um item' and never explains what the diligence_id identifies or how the two IDs relate, so it fails to compensate for the coverage gap.

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?

States a specific verb+resource pair ('Aprova a taxa do órgão para um item') and adds a notable side effect ('retoma a busca'), which distinguishes it from siblings like check_payment or buy_credits. It does not explicitly contrast itself with any sibling tool, keeping it below a 5.

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?

The instruction 'confirme com o usuário antes' gives an explicit precondition (user confirmation) before spending credits, which is real usage guidance. However, no alternative is named (e.g., when to use buy_credits or check_payment instead), and there is no stated condition for when the fee needs approval at all.

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.