Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Wholesale enquiries for businesses

get_b2b_wholesale
Read-only

Venue enquiry route. Request a current quote; no supply date, free tasting or draft programme is guaranteed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/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 the safety profile is covered. The description adds useful expectation-setting — no supply date, free tasting, or draft programme is guaranteed — which tells the agent what the response will and will not commit to. It stops short of describing the actual response content or any submission/auth requirements.

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?

Two short sentences, front-loaded with the route's identity and followed by the key limitation; nothing is padded. The wording is slightly terse to the point of being cryptic, but structurally sound.

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 zero-parameter, read-only enquiry tool with annotations covering safety, the description is minimally adequate but omits the central fact that it is a wholesale/B2B enquiry and what the agent receives back. An agent could misroute pricing or partnership questions to it.

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 nothing for the description to disambiguate; the baseline of 4 applies. The added caveats about non-guaranteed outcomes are the only extra semantics a no-param tool can carry.

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

Purpose2/5

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

The description calls it a "Venue enquiry route" and mentions requesting a quote, but never states that it is for B2B wholesale enquiries, despite the name and title claiming so. It never uses a clear verb+resource pair like "submit a wholesale enquiry"; the agent must infer the tool's actual function from the name and sibling context.

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?

It says it is an enquiry/quote route but gives no condition for choosing it over siblings such as get_pricing_and_delivery or get_partnership_info, which plausibly overlap. No when-not-to-use guidance or prerequisite is stated.

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