Skip to main content
Glama

Get one error issue

get_error_issue
Read-only

One issue with its status, history, 30 days of daily counts and recent occurrences. The newest occurrence has its stack and frames, the older ones are one-line summaries. Use it to see how an issue behaves over time. For a fix, get_error_issue_brief is shorter; for source lines and variables, use get_error_event.

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": {
      "issue_id": "<issue_id>"
    },
    "name": "get_error_issue"
  }
}

Input Schema

NameRequiredDescriptionDefault
issue_idYesIssue id, from list_error_issues
occurrencesNoHow many recent occurrences (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / occurrences
      Added value: +{
      +  "description": "How many recent occurrences (default 5)",
      +  "maximum": 50,
      +  "minimum": 1,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavioral detail beyond that: the payload includes 30 days of counts and a mixed occurrence list where only the newest has full stack frames while older entries are one-line summaries. It stops short of mentioning size limits or truncation behavior for large histories.

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 tight sentences with no filler: return payload first, then the newest-vs-older detail, then usage and routing. The most decision-relevant information is front-loaded and nothing is repeated from the schema or annotations.

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?

There is no output schema, so the description carries the burden of describing the response, and it does so adequately by enumerating status, history, counts and occurrence detail. A minor gap remains around response size and whether history or counts can be truncated for large issues.

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 both parameters are already documented and the baseline is 3. The description still earns credit by clarifying what 'recent occurrences' means in practice, namely that the newest entry is expanded with stack and frames while the rest are compressed, which helps an agent reason about how many occurrences to request.

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?

The description names the resource (one error issue) and enumerates exactly what it returns: status, history, 30 days of daily counts, and recent occurrences, with the newest carrying stack and frames. It also explicitly distinguishes itself from get_error_issue_brief and get_error_event, so an agent can identify the tool without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the intended use case directly ('Use it to see how an issue behaves over time') and routes two competing needs to named alternatives: brief data to get_error_issue_brief, source lines and variables to get_error_event. Both the when-to-use and the when-to-use-something-else conditions are present.

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