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?
Description adds value beyond annotations: deactivation vs deletion, historical events retained. Aligns with idempotentHint and destructiveHint. Clearly states ownership enforcement.
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, no waste. Front-loaded with action and key constraints.
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 one-param tool with annotations, the description covers purpose, constraints, side effects, and retention policy. No output schema needed; complete.
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 already documents 'id' as uuid returned by subscribe (100% coverage). Description only says 'by id', adding no new meaning beyond schema.
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 'Cancel a subscription by id' and distinguishes from siblings like subscribe and list_subscriptions by specifying effect (deactivate) and ownership enforcement.
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?
Gives clear context: ownership enforcement and that the subscription is deactivated not deleted. Does not explicitly state when not to use or alternatives, but the constraint is helpful.
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 tools overlap heavily: ask_pipeworx and ask_pipeworx_beta are described as currently identical, and deep_research/ask_pipeworx plus the many polymarket_* tools have adjacent intents that are easy to confuse. scan_competitor_ai_presence also directly wraps ai_visibility_check, so an agent can easily select the wrong tool for the same task.
Names are consistently snake_case, but the convention is mixed: some are verb-first (query_subgraph, introspect_schema, validate_claim), some are noun-first (entity_profile, polymarket_edges, pipeworx_trending), and some are bare verbs (remember, recall, forget). The repeated prefixes help, but there is no single predictable naming pattern across the set.
With 33 tools, this exceeds a reasonable single-server footprint, and the scope sprawls across data routing, prediction markets, AI visibility, npm dependencies, llms.txt generation, memory, and subscriptions. Many tools feel like separate mini-applications rather than one coherent toolkit for The Graph.
The Pipeworx data-research and prediction-market side is well covered with lookup, grounded answers, research, comparison, profiles, claims, subscriptions, and memory. However, the server's apparent namesake, The Graph, is thin: only query_subgraph and introspect_schema exist, with no subgraph discovery, status, or management tools.