Skip to main content
Glama

Delivery estimate

get_delivery_estimate
Read-onlyIdempotent

Use this when the user asks when a mug would arrive. Expected delivery window for an order placed now (Germany, DPD, UPS or DHL): production start rule (cutoff 14:00 Berlin time on business days), earliest and latest delivery date, plus the current workload (normal / elevated / high) with the estimated processing time until dispatch and the recent real average. Checkout also accepts a preferred date (arrive by / ship from), so a gift can be held back.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, yet the description still adds real substance: the 14:00 Berlin cutoff rule, workload states (normal/elevated/high), processing time to dispatch, and a recent real average. It does not say how volatile or cached the estimate is, which keeps it off a 5.

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?

The trigger sentence is front-loaded and every clause contributes: cutoff rule, date range, workload, average, preferred-date handling. It is packed into one long sentence, so a reader has to parse carefully, but there is no filler.

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 has to convey what comes back, and it does so in detail (earliest/latest date, workload level, processing time, recent average). The geographic and carrier limitation is disclosed; only the absence of any note on estimate reliability or staleness keeps it from a 5.

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 no parameters, so the baseline is 4. The description usefully scopes the answer to Germany and the DPD/UPS/DHL carriers, which frames what the returned estimate covers even though there is nothing to parameterize.

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?

States a concrete verb and resource ('Expected delivery window for an order placed now'), plus the exact user question that triggers it ('when a mug would arrive'). This clearly separates it from siblings like calculate_price or get_design_options.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit when-to-use trigger tied to a user question and mentions the checkout 'preferred date' variant, so the agent knows the relevant scenario. It stops short of naming alternatives or stating when not to call it, so it is not a full routing statement.

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