Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Pricing, packs, and delivery

get_pricing_and_delivery
Read-only

Current published pre-order prices and formats. Delivery eligibility, fees and payment methods must be confirmed at the live Shopify checkout; no dispatch date is confirmed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 genuinely useful behavioral caveats beyond that: prices are 'published pre-order' figures, dispatch dates are explicitly unconfirmed, and checkout is the authoritative source for delivery and fees. That prevents an agent from over-promising on shipping or release timing.

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 short sentences, front-loaded with what is returned and immediately followed by the limits on what can be concluded from it. Nothing is padded or repeated from the schema.

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?

With no input parameters and no output schema, the description carries the burden of indicating what comes back, and 'prices and formats' does that at a coarse level on top of the useful caveats about checkout and dispatch dates. A note on the shape of the pricing response (currency, pack sizes) would make it fully self-sufficient.

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; baseline 4 applies. No misleading parameter hints are introduced either.

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 concrete resource — 'current published pre-order prices and formats' — so an agent knows it returns pricing/packaging data rather than beer, brand, or FAQ content. It does not explicitly differentiate itself from siblings like get_subscription_plans or get_b2b_wholesale, which is the main gap.

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?

It sets a clear boundary: delivery eligibility, fees, and payment methods are not answerable here and must be confirmed at the live Shopify checkout, which usefully prevents an agent from treating this as a shipping-cost tool. However, it names no sibling alternative for related pricing questions (subscriptions, wholesale), so routing among pricing tools is left to inference.

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