List every coupon this operator has minted (newest first).
Each row carries the current times_redeemed counter — the
Studio renders a progress bar from this against total_uses.
RESTRICTED to operator — requires proof.
| Name | Required | Description | Default |
|---|---|---|---|
| dpop_token | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. States access restriction and data included, but lacks details on failure modes or 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Concise, three sentences front-loading purpose and data description. Lacks parameter explanation but otherwise efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Output schema is present but not detailed. Description covers purpose and data but omits parameter semantics and potential pagination or limits.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%. The description does not explain the dpop_token parameter or how to obtain the required proof.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Clearly states the tool lists coupons minted by the operator, ordered newest first, and distinguishes from sibling tools like cypher_list_my_coupons.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Specifies that the tool is RESTRICTED to operators and requires proof, but does not mention when to avoid this tool or compare with alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The set is heavily clustered: audit_why_exists, explain_capability, suggest_capability_why, and authorize_capability_why all answer the same basic 'why does this capability exist?' question and differ mainly in provenance/authority. Many status and provenance tools (adoption_status, session_status, service_status, issue_provenance, pr_provenance, symbol_provenance, service_provenance) also blur together without close reading.
The overwhelming majority of tools follow a predictable cypher_verb_noun pattern in snake_case, which provides strong naming consistency across a very large surface. Minor deviations such as cypher_oracle_about, cypher_oracle_how_to_join, cypher_which_service_handles, and cypher_what_realizes_capability are noticeable but do not break the overall pattern.
112 tools is an extreme count for a single MCP server, regardless of how well the clusters are named; it heavily burdens tool selection, context, and agent discovery. The set spans unrelated domains including payments, coupons, credentials, provenance, issues, patents, queries, pricing, and NOS transformations, which should be split into separate focused servers.
Many domain clusters have strong lifeycle coverage: COUPs have mint/list/update/delete/redeem, credentials have courier delivery/box status/update/delete/forget, and the named-query catalog has full CRUD plus published-tool management. Minor gaps exist—e.g., no generic list_services, no delete for capabilities, and no close/resolve action for issues—but most flows have no outright dead end.