Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Structured nutrition data (health platforms)

get_health_nutrition
Read-only

Indicative recipe-based nutrition per beer: per-serving and per-100ml calories, carbohydrates, protein, added sugar, ABV specification, allergens and dietary flags. Not measured production-batch results or medical advice.

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

Input Schema

NameRequiredDescriptionDefault
slugNoOptional beer slug; omit for the full lineup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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 adds genuinely useful provenance context that annotations cannot convey: values are 'indicative recipe-based' calculations, not measured production-batch results, and are not medical advice — a material accuracy caveat for an agent presenting allergen or ABV data. It still says nothing about coverage beyond the enum, error behavior for an unknown slug, or response shape.

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

Conciseness5/5

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

Two sentences, front-loaded with the returned content, then the disclaimers. The nutrient list is dense but each item is informative, and nothing is redundant padding.

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-required-parameter read-only lookup with a fully documented enum and no output schema, the description gives enough to call it correctly and to present results with the right caveats. Only the behavior for an invalid slug and the per-beer vs lineup return shape are left implicit, which the schema largely covers.

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?

Schema description coverage is 100% and the single optional slug parameter is documented in-schema, including the omit-for-full-lineup behavior; the enum constrains values fully. The description adds no parameter detail but does not need to, so the baseline is met.

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 specific resource (recipe-based nutrition per beer) and enumerates the exact fields available: per-serving and per-100ml calories, carbs, protein, added sugar, ABV, allergens, dietary flags. It is clearly distinguishable from sibling tools like get_beer or get_recipes, though the action verb is implicit rather than stated.

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?

Usage is only implied: an agent can infer this is the tool for nutrition/allergen/dietary questions. There is no explicit when-to-use, no routing to alternatives (e.g., get_beer for general product facts), and the closing sentence excludes data sources rather than competing 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