Skip to main content
Glama
Sign In

VibeAdmin

by solutions.easy-admin
OverviewDiscussionsAdmin

Application errors

get_errors
Read-only

Grouped application errors reported by the app (SDK captureError / POST /v1/errors): message, count, affected users, first and last seen, status. Pass id for one error's recent occurrences and affected users.

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

Input Schema

NameRequiredDescriptionDefault
idNoAn error group id, for the detail view.
sortNorecent
limitNo
queryNoMatches the message or error type.
statusNoopen

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already establish read-only, non-destructive, closed-world behavior, so the description only needs to add surrounding context. It does add provenance (errors come from the SDK captureError endpoint) and discloses that the same tool serves both a grouped list and a per-error detail view, but says nothing about pagination, limits, or result ordering beyond the schema defaults.

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, front-loaded with the resource and its returned fields, with the id-mode caveat last. Dense but not padded; the parenthetical endpoint reference is the only borderline item, and it is useful provenance.

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

Completeness3/5

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

With five optional parameters and no output schema, the description carries weight, and it does describe the shape of the returned records and the detail mode. It leaves gaps around filtering semantics (how query and status interact), limiting/sorting, and how this tool relates to the similar get_failed_jobs sibling.

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 40%, so sort, limit, and status rely on enums and defaults alone, which are largely self-evident. The description meaningfully explains id (switches to a detail view of recent occurrences and affected users) but never mentions query or sort, and reuses the word 'status' as a return field, which risks confusion with the status filter parameter.

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 names a specific resource (grouped application errors) and enumerates the fields returned (message, count, affected users, first/last seen, status), and it cites the ingestion source (SDK captureError / POST /v1/errors). It does not differentiate from the nearest sibling, get_failed_jobs, so an agent could hesitate between the two.

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

Usage Guidelines3/5

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

Usage is only implied: 'Pass id for one error's recent occurrences and affected users' tells the agent how to switch into a detail view but not when to prefer this over get_failed_jobs or query_events. There are no exclusions or prerequisites stated.

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

All VibeAdmin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources