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 already declare safety and idempotency; description adds that it lists 'active' subscriptions by default and specifies returned fields, but lacks details on pagination or rate limits.
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 with no redundant information; the main action is 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?
For a simple list tool with one optional parameter and strong annotations, the description fully covers purpose, usage, and return fields.
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 description indirectly clarifies the parameter's behavior by stating 'active subscriptions,' helping the agent understand the default without explicit parameter description.
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 verb 'list' and the resource 'subscriptions', and distinguishes from siblings like 'subscribe' and 'unsubscribe' by focusing on retrieval.
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 tells the agent to use this to review existing subscriptions before adding more or to find an ID to cancel, providing clear when-to-use guidance.
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.
The vast majority of tools are unrelated to the Inaturalist name, and several generic query/research tools overlap heavily (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, discover_tools, validate_claim). Even within the iNaturalist subset, search_observations and top_species both surface observation data and could be confused.
Naming is a mix of snake_case verb_noun patterns (search_observations, resolve_entity), brand-prefixed nouns (pipeworx_feedback, polymarket_edges), and bare nouns (recent_changes, entity_profile). There is no consistent convention across the set, only loose consistency inside a few small subgroups.
34 tools is too many for a server whose stated identity is Inaturalist, especially because only 3 of the 34 tools actually pertain to iNaturalist. The count is not extreme enough for a 1, but the massive scope mismatch makes the tool count feel inflated and unfocused.
As an iNaturalist server, the surface is severely incomplete: only observation search, taxa search, and top-species ranking exist, with no get-by-ID, create/update, identifications, projects, places, or user workflows. The 31 unrelated tools do not address the core domain implied by the server name.