Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

List all SOMA beers

list_beers
Read-only

Five styles with tasting profiles, ABV specification, indicative recipe-based nutrition, prices, availability and brewing notes. Nutrition is not measured production-batch data.

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": "list_beers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the catalog is a fixed set of five styles (suggesting no pagination or open-ended enumeration) and that nutrition figures are indicative recipe-based estimates rather than measured production-batch data, which is exactly the kind of data-quality caveat an agent needs before quoting numbers.

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

Conciseness4/5

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

Two short sentences, with the payload contents front-loaded and the data-quality caveat second. It is economically written, with only a minor cost that the lead is a bare noun phrase lacking a verb, which slightly hurts readability.

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

Completeness4/5

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

For a zero-parameter list tool whose annotations cover safety and which has no output schema, the description is nearly complete: it tells the agent what fields come back and warns that nutrition is estimated. The one gap is that 'five styles' is ambiguous about whether five beers or five style categories are returned, which matters for how the agent reports the results.

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 zero parameters and schema description coverage is 100%, so there is nothing to disambiguate; the baseline of 4 applies. The description correctly spends no words on argument semantics.

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

Purpose3/5

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

The description enumerates what each record contains (tasting profiles, ABV, nutrition, prices, availability, brewing notes) but never states the action, relying on the name/title 'List all SOMA beers' to supply the verb and scope. An agent can infer it returns the beer catalog, but the sentence itself reads as a content summary rather than a purpose statement, and it does not distinguish it from get_beer or get_health_nutrition.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer get_beer for a single beer or get_health_nutrition for details, and no statement that this returns the full list rather than a filtered subset. The only implicit signal is 'five styles', which hints at a small complete catalog but is not framed as usage guidance.

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