Skip to main content
Glama

explicar_erro

Retrieves the explanation for a calculation error code so users can understand what went wrong.

Instructions

Retorna a descrição de um código de erro devolvido pelo cálculo (ex: 'REG-011', 'CAL-001', 'VAL-001').

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": {
      "codigo": "<codigo>"
    },
    "name": "explicar_erro"
  }
}

Input Schema

NameRequiredDescriptionDefault
codigoYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description must carry the behavioral load. It discloses the useful context that the codes originate from the calculation, and the operation is implicitly a read-only lookup. However, it does not say what is returned for an unrecognized code, whether the response is plain text or structured, or which language the description is in.

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?

A single sentence with zero filler; the resource is named first and the examples are appended where they are immediately useful. Nothing needs trimming or reordering.

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 one-parameter lookup with no output schema, the definition covers the essential contract: given a code, return its description. Only the return format and unknown-code behavior are left undefined, which is a modest gap for a tool this simple.

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?

The schema has one parameter at 0% description coverage, so the description must compensate. It does so partially by supplying three example code values, which clarifies the expected format and hints at prefix families (REG, CAL, VAL). It still does not enumerate valid codes or explain what each prefix means.

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 and resource: returns the description of an error code produced by the calculation. The example codes ('REG-011', 'CAL-001', 'VAL-001') make the domain concrete. It does not differentiate against siblings, but none of the listed siblings appear to be error-lookup tools, so the gap is minor.

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?

Usage is implied by the phrase 'devolvido pelo cálculo' – call this when a calculation returned an error code. There is no explicit when-not guidance, no statement about what happens with an unknown or malformed code, and no mention of alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.