Skip to main content
Glama

Merge duplicate errors

runheed_merge_errors

Merges error groups that are the same bug into one: their events move to the target group (targetId) and new events with their fingerprints join it too. With groupByMessagePrefix, new events of the target's type whose message starts with that text also join it, for messages that differ only by an ID or a number. Returns what was merged.

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": {
      "targetId": "<targetId>",
      "errorIds": "<errorIds>"
    },
    "name": "runheed_merge_errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
errorIdsYesError groups to merge into the target (same project)
targetIdYesThe error group to keep
groupByMessagePrefixNoOptional message prefix: new events of the target's type whose message starts with it are grouped into the target

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare a non-readonly, non-idempotent, non-destructive mutation. The description adds valuable behavior: events move to the target, new events by fingerprint join it, prefix grouping affects future events, and a summary of what was merged is returned. It still does not state reversibility, permissions, or what happens to the source group records, so 4 rather than 5.

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?

Three sentences, front-loaded with the core merge action and followed by the prefix condition and return note. There is little waste; the wording is dense but readable.

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 merge mutation with annotations supplying safety flags and a fully described schema, the description covers the core action, event movement, prefix behavior, and return value. It leaves out the fate of source groups and reversibility, but the key invocation details are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema for groupByMessagePrefix (only for messages differing by an ID or number) and clarifies targetId as the group kept, which is useful semantic guidance.

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 states the specific action (merges error groups that are the same bug into one) and identifies the target via targetId. It is clear enough to distinguish merge behavior from read-only sibling tools, though it does not explicitly name when another tool such as resolve or ignore should be used instead.

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?

It gives implied guidance by saying to use this for duplicate errors ('the same bug into one') and explains the optional prefix use case. It does not state exclusions, prerequisites, or explicitly compare with resolve_error/ignore_error, so an agent must infer boundaries.

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.