cancel_merge
Cancel a staging intent (owner_token).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| merge_id | Yes | ||
| owner_token | Yes |
Progenly
by com.progenly
TDQS
C2/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must carry the full burden of behavioral disclosure. It merely states 'cancel,' implying a destructive or undo action, but does not describe side effects, reversibility, owner_token semantics, or any safety considerations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness2/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is minimal (one phrase), which is too brief to convey necessary information. True conciseness balances brevity with completeness; here, clarity is sacrificed.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness1/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given two required parameters, no output schema, and multiple related siblings, the description is severely incomplete. It fails to explain the tool's role in the merge lifecycle or provide parameter context, making it hard for an agent to use correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters1/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 0%, yet the description only mentions 'owner_token' in parentheses without explaining its meaning or relationship to merge_id. It adds no value beyond the schema, leaving both parameters unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose3/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description states 'Cancel a staging intent (owner_token),' which is a verb+resource combination indicating cancellation. However, it does not define what a 'staging intent' is, leaving ambiguity. It vaguely differentiates from sibling tools like 'stage_merge' but lacks clarity on the tool's exact scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives (e.g., when to cancel vs. lock or confirm). Context signals and sibling tools suggest a merge workflow, but the description offers no usage context or exclusions.
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.
TDQS
B3.2/5.0
Disambiguation5/5
Each tool addresses a distinct operation: merge workflows (stage, join, lock, confirm, cancel, status) are separate from birth queries (get, list, search, random, certificate, lineage, verify) and auxiliary functions (stats, revocations, colony handle verification). No two tools have ambiguous purposes.
Naming Consistency4/5
Most tools follow a clear verb_noun pattern (cancel_merge, get_birth, list_births), with minor exceptions like 'merge_status' (noun_verb) and 'random_birth' (adjective_noun). The convention is largely consistent and readable.
Tool Count4/5
16 tools is a reasonable count for a system handling both birth certificates and merge intents. The number is well-scoped, not excessive, and each tool contributes to covering the domain without redundancy.
Completeness4/5
The tool surface covers the full merge lifecycle (stage, join, lock, confirm, cancel, status) and birth querying (get, list, search, random, certificate, lineage). While there is no explicit tool to create a birth (it is a product of a merge), the set feels complete for the intended workflows.