Skip to main content
Glama

Get an error

runheed_get_error
Read-only

Returns one error group in full: message, status, counts, first and last seen, environment, agent context, the top stack frames and the latest breadcrumbs. If the error came back after it was marked resolved, it also shows the note it was resolved with, so you can see what the last fix tried. For a resolved error it reports whether the fix held: events since, releases deployed since and whether the fixing commit is live.

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": {
      "errorId": "<errorId>"
    },
    "name": "runheed_get_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorIdYesThe error ID to get details for

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare this a safe, non-destructive, closed-world read, so the bar is lower. The description still adds real value beyond them by disclosing what content comes back and a non-obvious behavioral trait: for errors that reoccurred after resolution it surfaces the original resolution note and reports whether the fix held (events since, releases since, whether the fixing commit is live). That conditional behavior is exactly the kind of thing annotations cannot express.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Content is front-loaded into a lead sentence plus its field list, then two sentences on the resolved/recurrence case, which is the genuinely surprising part. It is somewhat dense with enumerated fields, but no sentence is pure filler; the trailing "so you can see what the last fix tried" is the only mild redundancy.

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?

With no output schema, the description has to characterize the return payload, and it does so thoroughly, including the resolved-error reporting case. The remaining gap is failure behavior — what happens for an unknown or deleted errorId — which matters little against annotations that already establish the safety profile.

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?

There is a single required parameter (errorId) at 100% schema description coverage, so the schema already carries its meaning. The description says nothing extra about ID format, where to obtain it, or what happens with an invalid or stale ID, so it only meets the baseline for a fully documented schema.

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 opens with a concrete verb and resource — "Returns one error group in full" — and enumerates the specific fields (message, status, counts, first/last seen, environment, stack frames, breadcrumbs). That is far more specific than the bare name. It does not, however, distinguish itself from the closely named sibling runheed_get_error_context or say why you would pick this over runheed_search_errors, so it stops short of 5.

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 can infer this is the detail-fetch tool to call once it has an errorId. There is no explicit when-to-use statement, no mention of feeding an ID from runheed_search_errors, and no exclusion telling the agent when runheed_get_error_context or runheed_get_recent would be the better call.

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.