Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Non-alcoholic beer rules by country

get_na_beer_rules
Read-only

How countries and territories in Asia and the Middle East define, label and sell non-alcoholic beer: the alcohol level at which a drink counts as alcoholic, the terms a label may use, the main sale rules, and a link to the law, regulator or official standard behind each fact. Also what official halal bodies have published. General information, not legal advice. Pass a country to get one row; leave it out to get every row. SOMA itself delivers in India only.

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

Input Schema

NameRequiredDescriptionDefault
countryNoA country or territory, e.g. 'Japan', 'UAE', 'Dubai', 'Saudi Arabia', 'Korea'. Leave out for all rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

The annotations already establish that this is a read-only, closed-world reference lookup. The description adds useful behavioral context: the geographic coverage, linked legal sources, halal-body coverage, legal disclaimer, and the fact that SOMA delivers only in India. It does not describe rate limits, data freshness, or exact return structure, but those gaps are minor for this reference tool.

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?

The description is front-loaded and information-dense, covering scope, content, parameter behavior, disclaimer, and geographic limitation without wasted words. It is slightly long for a single-parameter reference tool, but most sentences carry useful context.

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 read-only lookup with one optional parameter and no output schema, it explains the content categories and source links well enough for an agent to know what will be returned. It could be slightly more explicit about the shape of each row, but the description is largely complete.

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 schema already documents the optional country parameter and its omission behavior. The description reinforces that passing a country returns one row while omitting it returns all rows, but adds little semantic detail beyond the schema.

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

Purpose5/5

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

The description clearly states that this tool returns non-alcoholic beer rules by country, including alcohol thresholds, labeling terms, sale rules, legal sources, and halal publications. This is a specific regulatory reference tool, easily distinguished from sibling product, pricing, and brewing tools.

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

Usage Guidelines4/5

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

It explicitly says to pass a country for one row or omit it for every row, and it clarifies the geographic scope and that the information is general rather than legal advice. It does not explicitly compare against sibling tools or state when not to use it, so it falls short of full 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