Skip to main content
Glama

Shipping to a US state

ships_to
Read-onlyIdempotent

How buying works for a US state: Red Good Wine's own non-alcohol products ship within the US; wine, beer and spirits are sold and shipped by the licensed shops, each deciding where it ships (bottle_offers lists each shop's states when known).

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": {
      "state": "<state>"
    },
    "name": "ships_to"
  }
}

Input Schema

NameRequiredDescriptionDefault
stateYesTwo-letter US state code, e.g. CA.

Output Schema

NameRequiredDescriptionDefault
stateYes
alcoholYes
own_products_shipYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare this a read-only, idempotent, non-destructive, closed-world lookup, so the safety bar is low. The description adds genuinely useful domain behavior: non-alcohol products ship within the US from the retailer itself, while wine/beer/spirits are sold and shipped by licensed shops that each set their own coverage. Return shape is not described, but an output schema exists.

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?

One sentence carries all the content, and the key split (own products vs. licensed shops) is front-loaded. The parenthetical about bottle_offers is well-placed as a pointer rather than padding. Slight density makes it harder to scan than a shorter verb-led opening would be.

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?

The tool is simple (one required parameter) and an output schema covers return values, so the description only needs to convey the business rule. It does that, including the important nuance that coverage varies by shop rather than being fully answerable here. It could be slightly more explicit that per-shop detail must come from bottle_offers.

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%, with the single parameter documented as a two-letter US state code with length constraints. The description's repeated emphasis on 'US state' reinforces the scope but adds no format, normalization, or edge-case detail beyond the schema. Baseline 3 is appropriate.

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 explains that the tool answers 'how buying works for a US state', splitting the answer into own-brand non-alcohol shipping nationwide versus alcohol being shipped by individual licensed shops. It also names the sibling bottle_offers and its role, so an agent can tell the two apart. The phrasing is a bit roundabout (a noun phrase rather than 'returns shipping availability for a state'), which keeps it from a 5.

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?

The description points at bottle_offers as the place where per-shop state lists live, which implies a division of labor, but it never states explicitly when to call ships_to versus bottle_offers. Usage is inferable from the content rather than declared. No exclusions or prerequisites are given.

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