Skip to main content
Glama

Check delivery

check_delivery
Read-only

Can we deliver to a UK postcode, how, and on which dates. Pass the model to get dates that allow for the item's stock. Returns own_team (London and the South East), palletline_kerbside (rest of mainland Great Britain, with charge) or not_available, with available dates.

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": {
      "postcode": "<postcode>"
    },
    "name": "check_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoModel number (optional)
postcodeYesUK postcode, e.g. HA4 8NW

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, and the description adds useful behavior beyond that: possible return categories (own_team, palletline_kerbside, not_available), the charge associated with palletline_kerbside, and date availability. It does not cover edge cases or error behavior, so it is strong but not exhaustive.

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?

The description is three compact sentences with no wasted text. It front-loads the core question and then adds the model-specific behavior and return values in a logical order.

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 output schema, the description usefully explains the possible return outcomes and dates. It is nearly complete for this read-only two-parameter tool, though it could clarify whether invalid or non-UK postcodes produce not_available or another error.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaning for the optional model parameter by explaining that it enables dates compatible with item stock. The postcode parameter is already well documented in 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 states a specific action and resource: checking whether delivery is possible to a UK postcode, how, and on which dates. It clearly distinguishes this from sibling product, basket, and store tools by naming delivery methods and availability outcomes.

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 implied: use it to check UK postcode delivery and pass the model to account for item stock. The description does not explicitly state when not to use it or name an alternative tool, so guidance is adequate but not complete.

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