Skip to main content
Glama
rtc-calculadora-mcp

rtc-calculadora-mcp

by tmoreiradev

descrever_erro

Explains calculator error codes like REG-011 found in erros[].code, clarifying their meaning so users can interpret errors and troubleshoot inputs.

Instructions

Explica um codigo de erro da calculadora (ex.: REG-011), como os que aparecem em erros[].code.

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

Input Schema

NameRequiredDescriptionDefault
codigoYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it only says the tool 'explains' a code. It does not state that this is a read-only lookup, how it behaves for an unknown or malformed code (error vs. generic message), or whether the explanation is exhaustive or partial. The output schema covers the return shape, which offsets some but not most of the gap.

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?

One sentence, front-loaded with the action and resource, with the example and the provenance pointer packed in without waste. Nothing could be removed without losing information.

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 read-only lookup backed by an output schema, the description covers what the tool does and where inputs originate. The remaining gap is failure behavior for invalid codes, which is minor for a tool of this complexity.

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 0% — the single `codigo` parameter is a bare string with no description — so the description must compensate. It does partially, via the format example (REG-011) and the pointer to `erros[].code` as the source of valid values, but it never states case sensitivity, accepted prefixes, or whether codes outside the taxonomy are tolerated.

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 pairs a specific verb ("Explica") with a specific resource ("um codigo de erro da calculadora") and even gives a sample code, so the agent knows exactly what the tool produces. It does not explicitly distance itself from the sibling tools, though the error-code domain is distinctive enough in practice.

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 rather than stated: the reference to `erros[].code` tells the agent where valid inputs come from, which is a genuine contextual hint. There is no explicit when-to-use/when-not guidance, no mention of what to do with an unrecognized code, and no named alternative.

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