unsubscribeCancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Subscription id (uuid) returned by subscribe. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses non-destructive nature (deactivation) and ownership enforcement, adding context beyond annotations. No contradiction with annotations (destructiveHint=false matches deactivation).
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?
Two efficient sentences, front-loaded with action, no redundant information. Every sentence adds value.
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?
For a simple tool with one parameter and no output schema, the description covers ownership, deactivation, and data retention fully. Context is complete given annotations and schema.
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?
Single parameter 'id' with schema containing description 'Subscription id (uuid) returned by subscribe.' The description does not add meaning beyond the schema, and with 100% schema coverage, baseline of 3 is appropriate.
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 verb 'cancel' and resource 'subscription by id'. Distinguishes from siblings like 'subscribe' and 'list_subscriptions' by mentioning ownership enforcement and deactivation behavior.
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?
Explains ownership enforcement and that the row is deactivated, not deleted, preserving historical events. Provides clear context for when to use the tool, though no explicit alternative is mentioned.
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.
Several tool clusters have unclear boundaries. `ask_pipeworx_beta` is explicitly described as currently identical to `ask_pipeworx`, `discover_tools` overlaps with `suggest_questions`, and the six Polymarket tools (`bet_research`, `polymarket_edges`, `polymarket_arbitrage`, etc.) blur together for opportunity-finding. An agent would struggle to pick the right tool without reading every description carefully.
Naming is overwhelmingly consistent snake_case with a verb_noun or noun pattern (`ask_pipeworx`, `list_subscriptions`, `validate_claim`, `recent_changes`). The `polymarket_*` and `ask_pipeworx_*` families follow clear conventions. Minor deviations like `bet_research`, `entity_profile`, and `landprice_points` being noun-first are still readable and predictable.
32 tools is heavy for a server named 'Landprice' when exactly one tool (`landprice_points`) actually concerns land prices. The vast majority of tools constitute an unrelated general-purpose data research and prediction-market platform, making the count feel bloated and scattershot relative to the server's stated purpose.
For the actual broad scope revealed by the tools — structured data lookup, grounded verification, deep research, entity resolution, comparison, monitoring, and memory — the surface is reasonably complete with no obvious dead ends. However, for the 'Landprice' domain implied by the server name, coverage is nearly absent: only Japan is covered, with no other countries, address search, or property-level data.