Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

SOMA Club enquiries

get_subscription_plans
Read-only

SOMA Club is planned. Ask SOMA for current prices, coverage, delivery terms and start date before describing a plan as active or guaranteed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_subscription_plans"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description's real contribution is the disclosure that SOMA Club is not yet live and that any plan described as active or guaranteed would be inaccurate — useful behavioral context, but it says nothing about the shape, freshness, or completeness of the returned data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short sentence with no filler, which is good. But it is front-loaded with status trivia ('SOMA Club is planned') instead of the tool's function, so the most important information for tool selection arrives last or not at all.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter, read-only tool with no output schema, the description needs to convey purpose and the nature of results. It gestures at result topics (prices, coverage, delivery terms, start date) but never states that the tool returns subscription plan records, leaving a notable gap for an agent deciding whether to call it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The schema is an empty object and imposes no constraints the description would need to explain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The name and title suggest retrieving subscription plan information, but the description never says the tool returns plans or pricing data — it reads as a caution ('SOMA Club is planned') and an instruction ('Ask SOMA for current prices...'). The only hints at what it produces are the enumerated topics (prices, coverage, delivery terms, start date), which an agent must infer from a caveat rather than a stated purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is an implied trigger — consult this before describing a plan as active or guaranteed — which gives the agent a reason to call it. However, no alternatives are named (e.g. get_pricing_and_delivery), and the guidance is framed as a warning to the model rather than a routing rule between tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources