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?
Adds behavioral context beyond annotations: specifies fields returned, default active-only behavior. Does not contradict annotations.
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, front-loaded with action, no wasted words. Efficient and informative.
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?
Complete for this simple tool: lists main fields, mentions default behavior, gives use cases. Output schema not needed.
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%, so baseline 3. Description does not mention the include_inactive parameter, but schema describes it well. Context provides purpose but not parameter details.
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 tool lists the caller's active subscriptions, specifies returned fields, and gives usage context. Distinguishes from siblings like subscribe/unsubscribe.
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 says when to use (review monitoring before adding, find id to cancel). Provides clear context for use, though does not explicitly state when not to use.
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 are near-identical: ask_pipeworx and ask_pipeworx_beta are explicitly the same function, ask_pipeworx_grounded is the same router with a different response mode, and polymarket_edges/polymarket_arbitrage/polymarket_edge_tracker/polymarket_fill_risk all overlap on prediction-market edge detection. search vs search_within vs discover_tools also blur discovery boundaries. An agent would struggle to pick the right tool without reading every long description.
All names are snake_case and individually readable, so there's no chaotic style mixing. However, the pattern is inconsistent: bare verbs (search, recall, forget, subscribe), verb_noun (get_package, resolve_entity, scan_dependency), noun phrases (latest_version, recent_alerts), and compound prefixes (pipeworx_*, polymarket_*). The server is named 'Nuget' but the vast majority of tools carry pipeworx_ or polymarket_ prefixes, making the namespace feel like a grab-bag.
35 tools is far too many for a server ostensibly named 'Nuget' — only ~5 tools relate to NuGet package lookup (search, get_package, list_versions, latest_version, scan_dependency), and even scan_dependency is npm-only. The remaining ~30 tools belong to an unrelated Pipeworx research/markets/memory platform. The count is inflated by redundant variants (ask_pipeworx trio, six polymarket tools) rather than distinct functionality.
Judged by the server's stated purpose (NuGet), the surface is thin and has dead ends: search and version metadata are covered, but there's no package owner/publisher info, no readme/description body fetch, no download stats beyond totals, and scan_dependency targets the wrong ecosystem (npm). Judged by the actual dominant domain (Pipeworx), coverage is excessive and sprawling. The tool set fails to deliver a coherent, complete surface for either apparent purpose.