Skip to main content
Glama

signafAIde

Explain a signafAIde error code

signafaide_explain_error
Read-only

Use this when the user has a signafAIde error code, from the SDK (SignafaideError.code), the command line or the service's error body, for example chain_conflict, quota_exceeded, invalid_key, network or not_recorded. Returns what the code means, how to fix it and, for an error the service returns, the address of its entry in the error reference. An unknown code returns the list of known codes. It looks nothing up about any account or project and changes nothing.

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, for example chain_conflict.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description goes further by disclosing the response content (meaning, remediation, and a reference URL for service-returned errors) and the fallback behavior for unknown codes (returns the list of known codes). It does not describe output format or size of the known-code list, which keeps it just under 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.

Conciseness5/5

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

Front-loaded with the trigger condition ("Use this when the user has a signafAIde error code"), followed by sources, return contract, and a scope disclaimer. Every clause adds information; no filler or restatement of the name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry the return contract, and it does: meaning, fix guidance, reference URL for service errors, and known-code list for unknown input. For a single-parameter, read-only lookup tool this covers everything an agent needs to call it and interpret the result.

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 100% with one required parameter, so the baseline is 3. The description adds real value by enumerating valid code families (chain_conflict, quota_exceeded, invalid_key, network, not_recorded), which tells an agent the granularity and shape of acceptable values beyond the schema's single example.

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?

States a specific verb (explain) and a specific resource (a signafAIde error code), then enumerates where such a code comes from (SDK SignafaideError.code, CLI, service error body). No sibling tool in the listed set touches error codes, so the boundary is unambiguous from the name plus description alone.

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?

Gives a clear trigger condition: use it when the user has an error code, and it names the concrete sources those codes appear in. It also implicitly excludes other uses by noting it looks nothing up about any account or project and changes nothing. It does not name an alternative tool to use for adjacent questions, so it falls short of an explicit when/when-not/alternatives statement.

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.

Resources