Skip to main content
Glama

Get recent errors

runheed_get_recent
Read-only

Returns the error groups seen most recently, newest first, with status, type, message, route, top stack frame, event count, last-seen time and ID.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of recent errors to return
projectIdNoFilter by project id or slug (e.g. shop-api)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / projectId / description
      Previous value: -"Filter by project ID"New value: +"Filter by project id or slug (e.g. shop-api)"
  2. First observed

TDQS

B3.2/5.0
Behavior3/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 real value with the sort order and the returned field set, but says nothing about default result count, the 50 cap, empty-result behavior, or whether errors are deduplicated into groups.

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?

A single front-loaded sentence with the resource and ordering stated first and the field list trailing as supporting detail. The field enumeration is dense but justified since there is no output schema; nothing is redundant.

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 two-parameter, read-only list tool with no output schema, the description carries the important burden of describing return values and does so thoroughly. The remaining gap is routing guidance versus runheed_search_errors and runheed_get_error, which matters given six sibling tools.

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 100%, so both parameters are already documented, including the projectId filtering example and the limit bounds. The description adds only the ordering semantics ('newest first'), not any clarification of how limit or projectId affect the result set, so baseline 3 applies.

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?

Specific verb ('Returns') plus resource ('error groups') and an explicit ordering rule ('newest first'), followed by the exact fields returned. It is clear what the tool does, though it never contrasts itself with the sibling runheed_search_errors, so the boundary between 'recent' and 'search' is left to inference.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative; the closest sibling, runheed_search_errors, is never mentioned. Only the implicit signal 'seen most recently' suggests the triage/dashboard use case.

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.