Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

NA beer cocktail recipes and food pairings

get_recipes
Read-only

Non-alcoholic beer cocktail recipes (shandies, beer-mosa, michelada, stout float) with ingredients and method, plus the food pairing guide per beer.

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_recipes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/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 and the description does not contradict it. Beyond that, the description only restates content categories: it says nothing about whether the full recipe corpus is returned at once, whether it is a static catalog, or how the pairing guide is organized, which is the behavioral detail an agent would need.

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?

It is a single front-loaded noun phrase with no filler, and the enumerated examples are informative rather than padding. Slightly held back because the sentence fragment lacks a verb, giving no explicit statement that the tool returns or retrieves this content.

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?

With no parameters and no output schema, the description carries the burden of describing the payload, and it does so by naming both the recipe content (ingredients and method) and the companion food pairing guide. Missing only the expected volume or shape of the response, which is a minor gap for a parameterless lookup.

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, so there is no parameter meaning for the description to supply; the baseline of 4 applies. The description correctly avoids inventing filtering options that the empty schema does not support.

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

Purpose4/5

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

The description names the resource precisely (non-alcoholic beer cocktail recipes) and enumerates concrete subtypes (shandies, beer-mosa, michelada, stout float) plus an additional artifact, the food pairing guide per beer. That is far more specific than the title alone. It stops short of differentiating itself from siblings such as get_health_nutrition or get_beer, so it is clear but not sibling-aware.

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 or when-not-to-use guidance, no mention of prerequisites, and no routing to alternatives among the many get_* siblings. An agent can loosely infer this is the recipe/pairing source, but nothing tells it when this tool is preferred over get_beer or get_health_nutrition.

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