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. |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses ownership enforcement, deactivation vs deletion, and impact on historical events, adding meaningful context beyond annotations which already indicate mutation, idempotency, and non-destructiveness.
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 concise sentences front-load the primary action, followed by necessary behavioral details. No unnecessary words.
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, no output schema, and annotations present, the description fully covers purpose, constraints, and side effects.
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 has 100% coverage on the single parameter 'id' with description. The tool description adds minimal extra meaning ('by id') but is sufficient given high schema coverage.
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?
The description explicitly states the action ('Cancel a subscription by id') and the resource ('subscription'). It distinguishes itself from sibling tools like 'subscribe' and 'list_subscriptions'.
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?
Clearly states when to use ('you can only cancel your own subscriptions') and provides behavior detail ('row is deactivated not deleted'), helping the agent decide appropriately.
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.
Multiple tools overlap in purpose, especially the ask_pipeworx variants and the polymarket_* tools. An agent would struggle to distinguish between similar functions, increasing the risk of selecting the wrong tool.
Tool names use inconsistent conventions: some are snake_case (close_approaches), some are verb_noun (generate_llms_txt), and others mix styles (ask_pipeworx vs. deep_research). No clear pattern is maintained across the set.
At 35 tools, the server is bloated and unfocused. The majority of tools are unrelated to the 'Jpl Ssd' domain, which only has 4 relevant tools. The count is far too high for the stated purpose.
The JPL SSD coverage is minimal (only 4 tools), missing key functionalities like detailed object queries or bulk downloads. The remaining tools cover unrelated domains, so the surface is both incomplete for its primary domain and cluttered with off-topic tools.