Skip to main content
Glama

report_error

Publish a work failure as an error event to a task's project so the team sees it via get_context, and optionally flag your agent status as error when you cannot continue.

Instructions

Report a failure you hit while working, so the team sees it instead of it staying in your log. With task_id, publishes an error event (tagged error and the severity, kept 72h) to that task's project, where get_context shows it. With recoverable=false it also sets your agent status to error in the team directory. It does not move the task or comment on it: use add_comment for that.

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": {
      "error_message": "<error_message>"
    },
    "name": "report_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idNoUUID of the task the error belongs to. Without it nothing is published to a project; only the agent status changes (and only when recoverable=false).
severityNoSeverity: low, medium (default), high or critical. Also added as an event tag.medium
recoverableNoDefault true. Pass false when you cannot continue: your agent status is then set to error.
stack_traceNoOptional stack trace, command output or other detail, stored in the event payload.
error_messageYesWhat went wrong, in a sentence or two. Required and non-empty; its first 100 characters become the event subject.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.6
    • changedInput schema / properties / error_message / description
      Previous value: -"Error message."New value: +"What went wrong, in a sentence or two. Required and non-empty; its first 100 characters become the event subject."
    • changedInput schema / properties / recoverable / description
      Previous value: -"Whether the error is recoverable."New value: +"Default true. Pass false when you cannot continue: your agent status is then set to error."
    • changedInput schema / properties / severity / description
      Previous value: -"Severity: low, medium, high, critical."New value: +"Severity: low, medium (default), high or critical. Also added as an event tag."
    • changedInput schema / properties / stack_trace / description
      Previous value: -"Stack trace or details."New value: +"Optional stack trace, command output or other detail, stored in the event payload."
    • changedInput schema / properties / task_id / description
      Previous value: -"Related task ID."New value: +"UUID of the task the error belongs to. Without it nothing is published to a project; only the agent status changes (and only when recoverable=false)."
  2. First observedv0.1.1

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only declare this is a non-readonly, non-destructive, non-idempotent write; the description adds real operational detail — the event is tagged with 'error' plus severity, retained 72h, surfaced via get_context, and that recoverable=false mutates the agent's team-directory status. That is meaningful disclosure of side effects the annotations do not carry.

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 sentences, each earning its place: purpose/effect first, conditional behavior second, exclusion third. No repetition of the schema field list and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must convey what happens on return; it does — event published with tags and 72h retention, visible via get_context, plus the agent-status side effect. For a 5-param write tool with one required field, nothing an agent needs before calling is missing.

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 the baseline is 3; the description earns a step up by explaining the cross-parameter consequence — without task_id nothing is published and only the status changes, and only when recoverable=false. It doesn't add syntax/format detail beyond the schema, but the interaction semantics are genuinely useful.

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?

Specific verb ('Report') plus resource ('a failure you hit while working'), immediately followed by the effect ('so the team sees it instead of it staying in your log'). It also explicitly fences itself off from add_comment, so an agent can distinguish it from siblings without opening the 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?

Gives the conditional when: pass task_id to publish to a task's project, pass recoverable=false to also set agent status to error. It states the exclusion explicitly — 'It does not move the task or comment on it: use add_comment for that' — which is exactly the when-not/alternative guidance the dimension asks for.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.