Skip to main content
Glama

Stop ignoring an error

runheed_unignore_error
Idempotent

Moves one ignored error group (errorId), or up to 100 (errorIds), back to unresolved, so new occurrences alert again. Returns what changed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "runheed_unignore_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorIdNoThe error ID to unignore
errorIdsNoSeveral error IDs to unignore (up to 100)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / errorIds
      Added value: +{
      +  "description": "Several error IDs to unignore (up to 100)",
      +  "items": {
      +    "type": "string"
      +  },
      +  "maxItems": 100,
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "errorId"
      -]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and the description is consistent with all of them. It adds value beyond the annotations by disclosing the resulting state ('back to unresolved') and the operational consequence ('so new occurrences alert again'), plus a hint about the response ('Returns what changed'). It does not state what happens if an ID is not currently ignored or how partial failures in a 100-item batch are handled.

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 that front-loads the action and the state transition, then closes with the return note. No redundant restatement of the title or schema.

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 two-parameter state-change tool with no output schema and annotations covering the safety profile, the description covers purpose, precondition, effect, and return shape. Minor gaps remain around non-ignored IDs and batch partial-failure semantics, but nothing essential to invoking it correctly is missing.

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 100%, so the schema already documents both parameters and the 100-item cap, making 3 the baseline. The description's phrasing 'one ... or up to 100' does add a useful signal that the two parameters are alternatives for the same intent, which the schema (neither required, no oneOf) does not express.

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 and resource ('Moves one ignored error group ... back to unresolved') with scope in both singular (errorId) and batch (errorIds) form. The state transition to 'unresolved' implicitly and unmistakably distinguishes it from the ignore_error sibling as its inverse.

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 clear usage context by naming the precondition (the group is ignored) and the outcome (new occurrences alert again), which tells an agent exactly when this tool applies. It stops short of explicitly naming runheed_ignore_error as the counterpart or stating when not to use it.

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.