Skip to main content
Glama

errors

Read-onlyIdempotent

Why is my app broken, exceptions, stack traces, failures, recent errors, crash reports, debugging. One trace_id returns the complete ordered parent/child operation waterfall plus its correlated logs, errors, deploy failures, and journey events. No project lookup is required for that one-id path. Without a trace id, project_id returns the last 24h of failures from that project's functions. Each row carries kind: "exception" means nobody chose the outcome (an uncaught throw, or a 5xx) and "refusal" means a handler answered 4xx on purpose — a 401 from your own auth gate is a refusal, not a bug, and kind separates the two.

Example:

{ "project_id": "my-saas", "limit": 20 }
// Returns: [{ "timestamp": "2026-04-20T...", "path": "/api/users/signup", "status": 500, "message": "UNIQUE constraint failed: users.email" }, ...]

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax number of errors to return (default: 10, max: 100)
trace_idNoOptional 32-character trace id returned by the platform. When supplied, returns the ordered waterfall and all correlated evidence; project_id is optional.
project_idNoProject ID (UUID), subdomain, or slug — resolved server-side, no UUID lookup needed. 'default' also works when the account has exactly one project; multi-project accounts must name one (the error lists them).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare readOnly/idempotent, so the description carries real weight and delivers: the 24h retention window for the project path, what correlated evidence accompanies a trace, the returned row shape, and the `kind` distinction between exceptions and deliberate 4xx refusals. The refusal-vs-bug nuance is exactly the kind of behavioral context annotations cannot express.

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?

Front-loaded with a search-friendly problem framing, then the two modes, then the kind semantics, then a concrete example that usefully shows a return row. The keyword lead-in is slightly noisy but the example earns its space given there is no output schema.

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?

Covers both invocation paths, the output fields an agent must interpret (timestamp, path, status, message, kind), and the time bound on the project path. With no output schema present, the description supplies enough return-value context to use results correctly.

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 coverage is 100%, so all three parameters are already documented, including project_id resolution and trace_id's effect. The description mainly restates those semantics (trace_id makes project_id optional) rather than adding syntax or format detail, so baseline 3 applies.

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?

States a specific resource (errors/exceptions/stack traces) and cleanly splits the two retrieval modes: a trace_id returns an ordered parent/child waterfall with correlated evidence, while project_id returns the last 24h of failures. An agent can distinguish those paths from the description alone 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 Guidelines4/5

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

Explicitly says the trace_id path needs no project lookup and that project_id alone scopes to a project's last 24h, plus the 'default' shortcut for single-project accounts. It gives clear context for each path but no explicit when-not or named alternative tool, so it stops short of a 5.

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