Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Frequently asked questions

get_faq
Read-only

All customer FAQs: what SOMA is, ABV and trace alcohol, brewing method, styles, pricing, delivery, age policy, comparisons to other NA beers, subscriptions, recycling, and wholesale.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description's only added behavioral signal is 'All', implying a full unfiltered corpus dump rather than a targeted lookup. It does not describe the shape of the returned content or whether it is long-text versus structured entries, which matters for a read-only dump with no output schema.

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?

A single sentence, front-loaded with the scope ('All customer FAQs') followed by the enumeration. The long topic list is slightly list-like but each item earns its place by telling the agent whether a given question is covered. No filler or hedging text.

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, read-only FAQ retrieval with no output schema and no parameters, the essential information is which questions are answerable, and the description supplies that. The remaining gap is that it does not indicate volume or return format, but nothing an agent needs in order to call it correctly is missing.

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 the schema is an empty object, so there is no parameter semantics to explain and no gap to compensate for. The description correctly implies the tool is argument-free by listing all topics as a single unfiltered corpus.

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 a specific resource ('All customer FAQs') and enumerates the subject matter covered (SOMA, ABV/trace alcohol, brewing method, styles, pricing, delivery, age policy, comparisons, subscriptions, recycling, wholesale), so an agent knows exactly what content is returned. It does not, however, distinguish itself from siblings that cover overlapping topics such as get_pricing_and_delivery, get_brewing_process, or get_subscription_plans.

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 by the topic list: an agent can infer this is the broad catch-all for customer questions. There is no explicit when-to-use or when-not-to-use statement, and no pointer to the more structured sibling tools when a request maps to a specific topic like pricing or subscriptions.

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