Skip to main content
Glama

Delivery fee and minimum for a ZIP

delivery_fee
Read-only

Look up the delivery fee and minimum order for a Texas delivery zip code. Use when a customer asks what delivery costs or what the minimum order is for their area. ALWAYS pass event_date when the customer has mentioned their party date - minimum orders vary by date and the dated answer is exact. Without a date the answer is the general rule.

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": {
      "zip": "<zip>"
    },
    "name": "delivery_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit delivery zip code
event_dateNoEvent date YYYY-MM-DD, when the customer has mentioned it. Always include if known.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safe read-only profile (readOnlyHint=true, destructiveHint=false, closed-world), so the bar is lower. The description adds real behavioral context the annotations don't: minimum orders vary by date, a dated answer is exact, and an undated answer returns the general rule. That changes how the agent should interpret the result.

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?

Four short sentences, front-loaded with purpose, then trigger, then the most important parameter direction. Every sentence carries information the agent needs; nothing repeats the schema verbatim.

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?

For a two-parameter read-only lookup with no output schema, the description covers purpose, trigger, geography scope, and the date-dependency caveat. Only minor gap is that the shape of the response (fee plus a minimum, possibly with notes) is implied rather than described.

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 coverage is 100%, so the baseline would be 3. The description goes beyond the schema by explaining the consequence of event_date rather than just saying 'always include if known' — it says the dated answer is exact and omitting it yields the general rule. That's genuine added meaning.

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 specific verb and resource ('look up the delivery fee and minimum order') and scopes it to a Texas delivery zip code. That scope plus the fee/minimum framing clearly separates it from siblings like build_quote or prepare_checkout.

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 explicit triggers: when a customer asks what delivery costs or what the minimum order is for their area. It also tells the agent when to include event_date. It doesn't name a sibling alternative, but the customer-intent triggers are concrete enough to route correctly.

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