Skip to main content
Glama

Search error events

search_error_events
Read-only

Single occurrences across issues, newest first, or counts with group_by. Use it to answer which release or route an error hits, whether a person hit it, or what failed in one trace. Open one with get_error_event.

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

Input Schema

NameRequiredDescriptionDefault
levelNo
limitNoRows (default 25)
queryNoText in the message, or the issue's title or culprit
sinceNoAn ISO time, or 30m, 24h, 7d. Default 30 days, or all kept events with issue_id or trace_id
cursorNonext_cursor from the last answer
sourceNoDefault all
releaseNoText in the release: 2.0.77+185, or package@2.0.77+185
user_idNoAn account id, Fictura user id or device id
group_byNoCounts per release, route, level, environment or tag:name
issue_idNoOnly this issue
trace_idNo
environmentNo
include_consoleNoAlso count console lines from the app. Always on with issue_id or trace_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / release / description
      Previous value: -"Text in the release"New value: +"Text in the release: 2.0.77+185, or package@2.0.77+185"
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare this as a safe, read-only, non-destructive search. The description adds helpful behavior beyond that: results are newest first, group_by switches to counts, and single occurrences should be opened with get_error_event.

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?

Three compact sentences with no wasted wording. The main search behavior is front-loaded, followed by use cases and the follow-up tool.

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 13-parameter search tool with no output schema, the description covers the core result modes, ordering, and follow-up path. It is reasonably complete, though it could say more about pagination or grouped-count output shape.

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 77%, so most parameters are documented structurally. The description adds semantic mapping for group_by counts and use cases involving release, route, person, and trace, but it does not explain remaining parameters such as level, source, environment, or include_console beyond what the schema already says.

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 and two modes: single error-event occurrences across issues, newest first, or counts with group_by. It distinguishes event-level search from opening a single event by naming get_error_event, though it does not explicitly contrast with search_error_issues.

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?

It gives concrete use cases: identifying release or route, checking whether a person hit an error, or inspecting a trace. It also routes the agent to get_error_event for opening a single occurrence, but does not state exclusions against issue-level search.

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