Skip to main content
Glama

Get one error event in full

get_error_event
Read-only

One occurrence: frames with source lines and variables, request, tags, contexts, breadcrumbs, causes and trace id. Pass issue_id for its latest event, or event_id. Use it to see why one error happened. Long events give up variables, then library frames, then breadcrumbs, and truncated says what went: call again with section to read that part whole.

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

Input Schema

NameRequiredDescriptionDefault
limitNoRows, for frames, breadcrumbs and causes (default 100)
cursorNonext_cursor, for frames, breadcrumbs and causes
sectionNoRead one part whole instead of the whole event
event_idNoRead this event, from search_error_events or get_error_issue
issue_idNoRead this issue's latest event

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnly/non-destructive annotations by disclosing the truncation cascade for long events (variables first, then library frames, then breadcrumbs), the `truncated` marker that reports what was dropped, and the recovery path (re-call with a section to read that part whole). That is exactly the kind of non-obvious behavior an agent needs before trusting the response.

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?

Front-loaded with what the tool returns, then key selection, then the truncation caveat — a sound ordering with little waste. The truncation sentence is dense and slightly run-on, packing cascade order, the `truncated` field, and the remedy into one clause chain.

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 carries the return-shape burden and does so well, covering the event's parts and the degraded/truncated case. Remaining minor gaps are what a section-scoped read returns and how cursor paging behaves, though the schema covers the latter.

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%, so baseline is 3, but the description adds real meaning by linking truncation to the `section` parameter and by explaining the issue_id-versus-event_id choice in behavioral terms ('its latest event'). It still does not clarify how limit/cursor interact with section-scoped reads.

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?

Opens with a specific verb/resource framing ('One occurrence') and enumerates the exact payload: frames with source lines and variables, request, tags, contexts, breadcrumbs, causes, trace id. It also distinguishes the single-occurrence tool from issue-level siblings by routing to 'the latest event' of an issue.

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 explicit selection guidance between the two lookup keys ('Pass issue_id for its latest event, or event_id') and a clear purpose statement ('Use it to see why one error happened'). It does not name sibling tools such as search_error_events or get_error_issue as alternatives when you want a list or issue-level summary, leaving that routing to the schema descriptions.

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