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 that the row is deactivated (not deleted) and that historical events remain available via 'recent_alerts'. This adds behavioral context beyond annotations, which already indicate 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 sentences: first states purpose, second provides key behavioral details. No fluff, efficiently front-loaded.
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?
Covers purpose, ownership, and data lifecycle. Missing error handling details (e.g., invalid id), but the tool is simple and idempotent, so the description is largely sufficient.
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 coverage is 100% with a clear description of the 'id' parameter. The description adds no new semantic information beyond what the schema provides, meeting the baseline for high 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 clearly states the action (Cancel a subscription by id) and the resource (subscription). It is distinct 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?
Specifies ownership enforcement and that the subscription is deactivated, not deleted. Implicitly guides use for own subscriptions only, though no explicit alternative or when-not-to-use is given.
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.
Most tools have clearly distinct purposes, with detailed descriptions. However, a few tools like 'discover_tools' and 'suggest_questions' both serve exploratory functions and could cause confusion. Similarly, 'ask_pipeworx' and 'deep_research' overlap in scope but are differentiated by depth and account requirements. Overall, an agent can typically pick the right tool, but a few pairs require careful reading.
All names use snake_case and are generally readable, but the convention varies: some are verb_noun (e.g., 'resolve_entity'), some are noun_noun (e.g., 'entity_profile'), and a few are just verbs (e.g., 'remember', 'forget'). The 'polymarket_' prefix helps group related tools, but the diversity in patterns slightly reduces predictability.
With 32 tools, the set is slightly large but justified by the wide range of functionality: data querying, prediction markets, memory, subscriptions, and utilities. Each tool serves a distinct purpose, and the count is not excessive given the server's role as a gateway to thousands of data sources. It feels well-scoped for its domain.
The tool set covers most essential operations: querying data, entity profiles, comparisons, subscriptions, memory, and onboarding. Minor gaps exist, such as the lack of a generic subscription for all data changes or a way to list all available data packs directly. However, 'discover_tools' partially addresses this. Overall, the surface is comprehensive for the server's purpose.