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 provide readOnlyHint and idempotentHint. Description adds useful behavioral context: lists caller's own subscriptions, returns specific fields, and optional include_inactive filter. No contradiction.
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 purpose and return fields, no wasted words. Efficient and well-structured.
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?
Low complexity tool (1 optional param). Description plus annotations fully cover purpose, usage, safety, and return fields. No gaps.
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 single boolean parameter already described. Description does not add additional meaning for the parameter beyond schema, so baseline 3 is appropriate.
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?
Description clearly states 'List the caller's active subscriptions' with specific verb and resource, and distinguishes from subscription-related siblings like subscribe and unsubscribe by mentioning usage for review and finding id to cancel.
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 states when to use the tool: 'review what you're monitoring before adding more or to find an id to cancel.' Does not explicitly mention when not to use or name alternatives, but context is clear.
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.
Multiple tools have overlapping purposes: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all serve similar question-answering roles. The soil-specific tools are distinct but mixed with many general tools, causing confusion.
Naming conventions are inconsistent: some tools use snake_case (ask_pipeworx, list_soil_properties), others are compound nouns (suggest_questions, deep_research), and there is no uniform pattern like verb_noun across the set.
With 34 tools, the count is high but might be justified for a broad platform. However, the server name 'Soilgrids' suggests a focused soil data service, making the count feel excessive and unfocused.
For soil data, the three dedicated tools (list_soil_properties, soil_classification, soil_properties) cover basic needs but lack advanced queries. The general tools are extensive but introduce many gaps unrelated to soil, so overall completeness for the server's stated purpose is mediocre.