Skip to main content
Glama
clamp-sh

Clamp Analytics MCP Server

Official
by clamp-sh
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

errors.groups

Read-only

Identify and triage the most frequent or impactful bugs by retrieving deduplicated error groups with occurrence counts, unique affected users, and first/last seen timestamps for any time period.

Instructions

Errors deduplicated by server-computed fingerprint, with counts and first/last-seen timestamps. The triage view: which bugs are firing most often, affecting the most users, or showing up newly in the period.

Each group is one fingerprint (a bug). count is total occurrences in the period; users_affected is unique anonymous_ids that hit it; first_seen and last_seen show the time window the bug appeared in. sample_message and sample_type are pulled from one occurrence in the group — useful for the agent to surface a readable label.

Examples:

  • "what's broken right now" → period="today", sort_by="count"

  • "regressions that started this week" → period="7d", sort_by="first_seen"

  • "bugs hitting the most users" → sort_by="users_affected"

  • "what just stopped firing" → check last_seen against expected freshness

Limitations: only fingerprintable errors are grouped; events with neither message nor stack get a null fingerprint and are excluded from this view (they still show up in errors.list). Default sort is by count; pass sort_by to change. Default limit 50, max 200.

Pairs with: errors.list (drill into a fingerprint to see individual occurrences with full context); errors.timeline (chart the rate of one fingerprint to spot regressions or post-deploy regressions); traffic.compare (correlate a count spike with a deploy or campaign).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
project_idNoTarget project ID (e.g. "proj_abc123"). Required when the credential has access to multiple projects. If omitted and only one project is accessible, that project is used automatically. Call `projects.list` to discover available project IDs.
periodNoTime period. Use "today", "yesterday", "7d", "30d", "90d", or a custom range as "YYYY-MM-DD:YYYY-MM-DD" (e.g. "2026-01-01:2026-03-31"). Defaults to "30d".
limitNoMax rows to return (1-50). Defaults to 10.
sort_byNoOrder groups by total occurrences (default), unique users affected, most recent occurrence, or earliest occurrence. Sort is always descending.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
periodYes
sort_byYes
groupsYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Discloses behavioral traits beyond annotations: describes the grouping logic, exclusion of null-fingerprint events, default sort and limit, and the nature of the view. Annotations only indicate read-only, which this description supports without contradiction.

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?

Well-structured: starts with core purpose, then describes each output field, provides concrete examples, and ends with limitations and sibling references. Every sentence adds value without redundancy.

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?

Given the presence of an output schema (context signals), the description focuses on purpose and usage, adequately covering the output fields (count, users_affected, etc.) and pairing with other tools. No gaps for a triage-view tool.

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?

Despite 100% schema coverage, the description adds value with usage examples for each parameter. However, it contains a contradiction: says 'Default limit 50, max 200' while schema says limit 1-50, default 10. This inaccuracy reduces reliability.

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 clearly states it aggregates errors by fingerprint with counts and timestamps, and explicitly calls it 'the triage view'. It distinguishes itself from sibling tools like errors.list (individual occurrences) and errors.timeline (rate charting).

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?

Provides explicit examples of when to use the tool with different parameters (e.g., 'what's broken right now' → period='today', sort_by='count'). Also mentions limitations (only fingerprintable errors) and pairs with specific siblings for drill-down or correlation.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/clamp-sh/mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server