Skip to main content
Glama

errors

Read-only

Read grouped $error events for a project (GET /errors). Errors is a Pro read. A free account gets 403 PRO_REQUIRED, the same status and error code as POST /query, and that rejection is not metered. Each successful call counts as one metered read. Errors is the post-ship guardrail next to compare: after a ship, read errors for the same window before you keep the change. The group key is a SHA-256 fingerprint of the normalized message (URL query strings and hashes removed, then UUIDs, hex hashes, and numbers replaced), the source filename without query or hash, and the numeric line. There is no stack, and col is not part of the key. Each group includes fingerprint, a sample message, source, line, count, users, sessions, first_seen, last_seen, and up to 3 top_paths. count, users, sessions, and top_paths use the since/until window. first_seen and last_seen use every stored $error for that fingerprint. Groups with no event in the window are omitted. since defaults to 7 days and accepts 7d or YYYY-MM-DD. until defaults to today UTC. limit defaults to 20 and maxes at 100. new_since is a YYYY-MM-DD or an annotation title. A date is used directly. Any other string matches project annotations by exact title, then case-insensitive title, then note, then substring. Zero matches is 400. More than one match is 400 with matches listing occurred_at and title. The group new_since boolean is present only when this param is set, and is true when first_seen is on or after the resolved date. new_since_annotation is returned only when new_since matched an annotation. Every response includes approximate, a boolean. When approximate is true, caps is an array of the scan caps that were hit: distinct_triples and window_rows. There is no singular cap field. A large project stays 200. The response also includes truncated.

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": {
      "project": "<project>"
    },
    "name": "errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax groups. Defaults to 20 and maxes at 100
sinceNoLookback window: 7d or YYYY-MM-DD. Defaults to 7 days
untilNoInclusive end date YYYY-MM-DD. Defaults to today UTC
projectYesProject name or ID
new_sinceNoYYYY-MM-DD or an annotation title. Zero matches is 400. More than one match is 400 with matches of occurred_at and title

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

The verb 'Read' and the annotations (readOnlyHint=true, destructiveHint=false, openWorldHint=false) already establish the safety profile, yet the description adds substantial context beyond that: Pro metering ('each successful call counts as one metered read'), the unmetered rejection path, the group-key construction, window semantics, and the fact that groups with no event in the window are omitted. The only gap is the caps and truncation behavior; the description names the fields but does not explain what it means when truncation occurs or how severe it is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, but the description is a ~350-word single block with no structural breaks and several deep internals, such as how the SHA-256 fingerprint is built. The lack of an output schema justifies explaining return fields, but the hash-normalization detail and repeated statements about default windows exceed what an agent needs to select and call 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 correctly compensates by enumerating the returned fields (fingerprint, message, source, line, count, users, sessions, first_seen, last_seen, top_paths) and the approximate/truncated envelope. The annotations cover safety, so nothing critical about invocation is missing. The only shortfall is that behavior under truncation is never explained.

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 the schema already documents all five parameters, giving a baseline of 3. The description's added meaning, including the resolution order for new_since (exact title, case-insensitive title, note, then substring), its echo field, and the fact that count/users/sessions/top_paths use the window while first_seen/last_seen do not, is genuinely useful but mostly restates window semantics rather than deepening parameter choices. The new_since resolution ladder is a real addition, though it is narrower than what a 4 would require.

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 states a specific verb and resource ('Read grouped $error events for a project') and pins the endpoint (GET /errors). It also tells the agent how this tool differs from the compare sibling: 'Errors is the post-ship guardrail next to compare: after a ship, read errors for the same window before you keep the change.' A specific purpose is complemented by a clear dividing line from the nearest sibling.

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?

The description gives a concrete usage trigger ('after a ship, read errors for the same window before you keep the change') and states the access precondition (Pro read; free accounts get 403 PRO_REQUIRED). It never names a case where this tool should not be used, or any alternative other than compare. The context is clear, but the exclusions are thin.

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