Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Get one SOMA beer

get_beer
Read-only

Detailed specification and indicative recipe-based nutrition, not measured production-batch results. Beer slug: lager, ipa, belgian-wit, stout, stout-caffeinated.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_beer"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBeer slug: lager, ipa, belgian-wit, stout, stout-caffeinated

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, non-open-world lookup. The description adds useful data-quality context by stating that nutrition is recipe-based and indicative rather than measured production-batch results, though it does not describe behavior for invalid slugs or error cases.

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?

The first sentence is useful and front-loads the important caveat about indicative nutrition. The second sentence duplicates the schema's slug enum almost verbatim and therefore does not fully earn its place.

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 simple one-parameter read-only lookup with annotations and full schema coverage, the description is adequate about the data's nature and provenance. However, it does not clarify the relationship to sibling tools such as list_beers or get_health_nutrition, leaving selection guidance incomplete.

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

Parameters3/5

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

Schema description coverage is 100%, and the single slug parameter is fully enumerated with its allowed values. The description repeats the same slug list without adding format, matching, or fallback semantics beyond what the schema already provides.

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 clearly identifies the resource as a single beer and specifies the returned content as detailed specification plus indicative recipe-based nutrition. It does not explicitly use a retrieval verb or name sibling tools such as list_beers, so sibling differentiation is only implied by the singular 'beer' scope.

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 explicit guidance on when to use this tool versus list_beers, get_health_nutrition, or get_recipes. The slug enumeration describes an input rather than a usage condition, leaving the agent to infer that this is the single-beer lookup.

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