list_revocations
List revoked certificates.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Progenly
by com.progenly
TDQS
A3.5/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description bears full responsibility for behavioral disclosure. It only states the action without details on ordering, pagination, idempotency, or any constraints, which is insufficient for an agent to understand side effects.
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?
The description is a single sentence with no wasted words. It is appropriately sized for a simple tool with no parameters.
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?
Given zero parameters and no output schema, the description is minimally complete. However, it lacks context about the scope of 'revoked certificates' (e.g., all or filtered) and does not imply ordering or behavior, leaving gaps for the agent.
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?
There are zero parameters and schema coverage is 100%, so the description adds no parameter info. Per guidelines, baseline is 4 as there is nothing to describe beyond the schema.
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 'List revoked certificates' clearly states the verb (list) and resource (revoked certificates), distinguishing it from sibling tools like get_certificate (single) and search_births (search). It is specific and unambiguous.
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 usage guidelines are provided. The description does not indicate when to use this tool vs alternatives like get_certificate or search_births, nor any prerequisites or context.
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.