Skip to main content
Glama

Search error issues

search_error_issues
Read-only

Find an issue by text in its title or culprit, across every issue the app has. Use it when you know the error message, exception type or function. Same filters and rows as list_error_issues.

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_issues"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoDefault last_seen. new = first seen most recently
levelNo
limitNoRows (default 25)
queryNoText to look for in the title or culprit
sinceNoLast seen since: an ISO time, or 30m, 24h, 7d
cursorNonext_cursor from the last answer
sourceNoThe server, the app, or both (default all)
statusNoWhich issues (default unresolved)
releaseNoText in a release the issue was seen in: 2.0.77+185, or package@2.0.77+185
platformNoLike python, ios, android
environmentNoIssues with an event in this environment
include_sparkNoAdd a 14-day sparkline per row (default false)
include_legacyNoAlso list issues grouped before grouping v2 (default false)
include_consoleNoAlso list console lines from the app (default false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / release / description
      Previous value: -"Text in a release the issue was seen in"New value: +"Text in a release the issue was seen in: 2.0.77+185, or package@2.0.77+185"
  2. Changed13 schema fields changed
    • addedInput schema / properties / cursor
      Added value: +{
      +  "description": "next_cursor from the last answer",
      +  "maxLength": 300,
      +  "type": "string"
      +}
    • addedInput schema / properties / environment
      Added value: +{
      +  "description": "Issues with an event in this environment",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / include_console
      Added value: +{
      +  "description": "Also list console lines from the app (default false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / include_legacy
      Added value: +{
      +  "description": "Also list issues grouped before grouping v2 (default false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / include_spark
      Added value: +{
      +  "description": "Add a 14-day sparkline per row (default false)",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / level
      Added value: +{
      +  "enum": [
      +    "fatal",
      +    "error",
      +    "warning",
      +    "info"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit / description
      Added value: +"Rows (default 25)"
    • addedInput schema / properties / platform / description
      Added value: +"Like python, ios, android"
    • addedInput schema / properties / release / description
      Added value: +"Text in a release the issue was seen in"
    • addedInput schema / properties / since
      Added value: +{
      +  "description": "Last seen since: an ISO time, or 30m, 24h, 7d",
      +  "maxLength": 40,
      +  "type": "string"
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Default last_seen. new = first seen most recently",
      +  "enum": [
      +    "last_seen",
      +    "events",
      +    "users",
      +    "new"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / source
      Added value: +{
      +  "description": "The server, the app, or both (default all)",
      +  "enum": [
      +    "backend",
      +    "frontend",
      +    "all"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / status / description
      Added value: +"Which issues (default unresolved)"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real value the annotations cannot: that the search scope is limited to title and culprit only (not stack traces, events, or message bodies) and that the returned rows and filters are identical to list_error_issues. It does not say whether matches are relevance-ranked or simply sorted by last_seen, which is a minor remaining gap.

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 short sentences, front-loaded with the verb and scope, then the usage trigger, then the sibling relationship. Nothing is wasted and no sentence repeats another.

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 14-parameter read tool with no output schema, the description covers what the tool searches and how its result shape relates to list_error_issues, while the schema handles the filter semantics in detail. A small gap remains around result ordering/pagination expectations beyond what the cursor field states.

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 description coverage is 93% and 4 of the 14 parameters carry enums, so the schema already documents nearly everything, including the query field's title/culprit scope. The description's parameter-adjacent content largely restates the schema's query description, so it meets the baseline without adding syntax or format detail beyond it.

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?

"Find an issue by text in its title or culprit, across every issue the app has" gives a specific verb (find), a specific resource (issue), and the exact search field scope (title/culprit). The closing note "Same filters and rows as list_error_issues" lets an agent separate it from the listing sibling without opening either schema.

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?

"Use it when you know the error message, exception type or function" states a concrete selection condition, and the reference to list_error_issues signals the relationship to the browsing tool. It stops short of an explicit exclusion (e.g., 'use list_error_issues when you have no query text'), so it is clear context without full routing guidance.

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