Skip to main content
Glama

Virág — Manhattan flower delivery

Check delivery availability

check_delivery

Check if a bouquet can be delivered to a ZIP code on a date. Use before create_order.

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": "check_delivery"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYes5-digit ZIP code of the recipient
delivery_dateNoYYYY-MM-DD (New York time). Omit for earliest.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It implies a read-only availability check and gives ordering context, but never states whether it is side-effect free, what it returns (a boolean, a reason for unavailability, alternate dates), or how it behaves for unsupported ZIPs. Useful but incomplete for an unannotated tool.

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 sentences, zero filler, with the core action and the sequencing advice both front-loaded. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter query this is close to adequate, and the sequencing hint is valuable. However, with no output schema and no annotations, the description should say what the check returns and how a negative result should be interpreted, since that is the entire point of calling it before create_order.

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 coverage is 100%, and the schema already documents both parameters more richly than the description does, including the New York time zone and 'omit for earliest' behavior for delivery_date. The description adds no syntax or semantic detail beyond restating the ZIP and date inputs, so the baseline 3 applies.

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 states a specific verb and resource: 'Check if a bouquet can be delivered to a ZIP code on a date.' An agent can immediately tell this is a delivery-availability lookup rather than an order mutation or bouquet listing. It falls short of a 5 only because it does not explicitly contrast itself with other siblings beyond naming create_order as the follow-up step.

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?

'Use before create_order' gives explicit sequencing guidance, telling the agent this is a pre-flight validation step rather than an order-placing call. It does not spell out when-not-to-use cases (e.g., re-checking after a successful order), but the relevant context is clear.

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.