Skip to main content
Glama

Get an issue brief and a fix prompt

get_error_issue_brief
Read-only

Use this first when asked to fix an error. One issue condensed: in-app frames with their source lines, the request, tags, breadcrumbs before it, log lines from the same trace, facets (release, OS, device, route), cause chain, and a ready-to-use fix prompt.

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

Input Schema

NameRequiredDescriptionDefault
issue_idYesIssue id, from list_error_issues

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/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 safety is covered. The description adds substantive value beyond that by disclosing the shape of the response — frames with source lines, request, tags, preceding breadcrumbs, same-trace logs, facets, cause chain, and a generated fix prompt — which tells the agent this is a synthesized, pre-digested view rather than raw events.

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?

Two sentences, and the most actionable instruction ('Use this first when asked to fix an error') is front-loaded. The second sentence is a long comma-separated enumeration that reads as a run-on, though each item carries information an agent would otherwise have to discover by calling the 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?

With no output schema, the description bears the burden of explaining return content, and it does so comprehensively down to the included fix prompt. What it omits is practical scale information — whether the brief can be truncated for very large issues, and that it requires a valid issue id obtained elsewhere.

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?

There is a single required parameter and the schema documents it fully (uuid format plus the note that it comes from list_error_issues), so the baseline is already high. The description adds no further parameter guidance, but with one fully-described parameter there is little left to compensate for.

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 concrete verb and resource ('One issue condensed') and enumerates exactly what the payload contains, so an agent knows it returns a single-issue diagnostic bundle rather than a list. It does not name the sibling get_error_issue or explain how the brief differs from that tool's full view, which keeps it short of a 5.

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 this first when asked to fix an error' gives an explicit entry-point condition tied to a task type, which is real routing guidance. It stops short of stating when NOT to use it or naming the alternative (e.g. get_error_issue for raw detail), so the exclusion half is absent.

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