list_subscriptionsList the caller's active subscriptions. Returns id, type, params, created_at, last_fired_at, fire_count for each. Use this to review what you're monitoring before adding more or to find an id to cancel.
| Name | Required | Description | Default |
|---|---|---|---|
| include_inactive | No | Include cancelled subscriptions in the response (default false). |
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?
Annotations indicate readOnlyHint, idempotentHint, and destructiveHint false. Description adds behavioral detail: returns specific fields and defaults to active subscriptions only, with optional inactive inclusion. No contradictions.
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: first states purpose and output fields, second provides usage guidelines. No redundant information.
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 optional parameter and no output schema, the description covers return structure, functionality, and usage context thoroughly.
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% and schema already describes the parameter. Description clarifies the default behavior ('active' vs include_inactive) but adds no new syntax or format 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?
The description states the tool lists the caller's active subscriptions, specifies return fields (id, type, params, etc.), and distinguishes it from sibling tools (subscribe, unsubscribe) by its review purpose.
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?
Explicitly instructs when to use: 'Use this to review what you're monitoring before adding more or to find an id to cancel.' Provides clear context for tool selection.
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 have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are currently identical, deep_research and ask_pipeworx both answer broad factual questions, and the polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_edge_tracker, polymarket_fill_risk, bet_research) cover heavily overlapping edge/arb research territory. An agent could easily route a query to the wrong one.
Most tools use snake_case, but there is no consistent verb_noun pattern: ask_pipeworx, deep_research, bet_research, recent_changes, remember/recall/forget, generate_llms_txt, realestateapi_property_detail, and polymarket_edges all follow different structural conventions. The server name Realestateapi also does not match the broader Pipeworx/polymarket tool set.
34 tools is above the 25+ threshold for a heavy, hard-to-navigate surface, especially for a server named Realestateapi where only 3 tools actually concern real estate. Many tools are generic utilities, memory helpers, feedback channels, and prediction-market tooling that feel unrelated to the apparent real-estate API scope.
For a real-estate-focused server, the surface is significantly incomplete: property search, property detail, and skip-trace cover only basic owner/value lookups. Missing obvious real-estate capabilities like comparable sales, tax history, market trends, school/flood data, and listing lifecycle operations create notable gaps an agent would need to work around.