Skip to main content
Glama

Explain a signafAIde error code

signafaide_explain_error

Explains what a signafAIde error code means and how to fix it for codes such as chain_conflict, quota_exceeded, invalid_key, network, and not_recorded.

Instructions

What a signafAIde error code means and how to fix it, e.g. chain_conflict, quota_exceeded, invalid_key, network, not_recorded.

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": {
      "code": "<code>"
    },
    "name": "signafaide_explain_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesThe error code, e.g. from SignafaideError.code or the service's error body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose that the response includes both meaning and a fix, which is real behavioral value, but it says nothing about whether the catalog is static or live, whether an unknown code errors or returns a generic answer, or whether any auth/service state is required.

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 meaning-plus-remediation promise, then the examples. Nothing is padded and nothing needs trimming.

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 single-required-param lookup with no output schema, the description covers what goes in and what comes out (meaning and fix). The only real gap is unknown-code behavior, which is minor at this complexity level.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100% and the schema explains where the code comes from (SignafaideError.code or the service error body). The description adds the concrete code vocabulary — chain_conflict, quota_exceeded, invalid_key, network, not_recorded — which meaningfully tells the agent what shape of value is expected.

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 states a specific resource (a signafAIde error code) and a specific outcome (its meaning plus remediation), and the listed example codes make the domain concrete. It is a noun phrase rather than a verb phrase, but an agent can still tell this apart from setup/init/verify siblings.

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 only implied: an agent should call this when it holds an error code. There is no explicit when-to-use statement, no mention of what to do for unknown codes, and no routing to or from sibling tools.

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