Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

pizzahut_delivery_estimate

Check if a Pizza Hut store delivers to an address and get the estimated delivery fee and pickup/dropoff times using order subtotal, without placing an order.

Instructions

Check Pizza Hut delivery serviceability and estimated fee for one store and address. Checks whether a Pizza Hut restaurant's delivery integration can deliver to a given address and, when it can, the estimated delivery fee (broken down by fee line item) and pickup/dropoff time. This reads the same checkout-time estimate Pizza Hut's own site calls -- it does not add an item to a cart or place an order, and takes no payment or account information. serviceable is true only when the upstream returned a real estimate; a false value with reason populated covers every other case seen live, such as the requested delivery_provider not being enabled at that store. For the default INTERNAL provider, a serviceable result does not by itself confirm the address is within a real deliverable radius -- see this endpoint's markdown doc for the caveat. order_subtotal materially affects the fee estimate, so it is required rather than defaulted. pickup_at defaults to 30 minutes from now (an "order now" style estimate) when omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityYesDelivery address city
stateYesDelivery address state, two-letter code
address1YesDelivery address line 1
address2NoDelivery address line 2
latitudeYesDelivery address latitude
longitudeYesDelivery address longitude
pickup_atNoRFC3339 pickup time (default 30 minutes from now)
postal_codeYesDelivery address postal code
country_codeNoDelivery address country code (default US)
store_numberYesPizza Hut's store number, from /pizzahut/stores
order_subtotalYesOrder subtotal before fees, in dollars
delivery_providerNoDelivery provider to check (default INTERNAL)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / delivery_provider / enum
      Added value: +[
+  "DOORDASH",
+  "MOCK_DOORDASH",
+  "INTERNAL"
+]
  2. Addedv1.16.2

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so thoroughly. It explains the read-only nature, the exact semantics of 'serviceable' and 'reason,' the INTERNAL provider caveat, and the default behavior for pickup_at. This goes well beyond a minimal description and gives an agent the behavioral context needed to interpret results correctly.

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 dense but every sentence earns its place: purpose, side-effect profile, result semantics, provider caveat, and parameter defaults. It front-loads the core purpose before diving into edge cases, and it avoids repetition of schema content.

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

Completeness5/5

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

Despite having no output schema and no annotations, the description covers the key behavioral and result semantics an agent needs: serviceable/reason meaning, fee line items, pickup/dropoff time, the INTERNAL provider caveat, and required/default parameter behavior. It even points to markdown docs for a known caveat, making it sufficiently complete for correct invocation.

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. The description adds meaningful parameter context beyond the schema: order_subtotal is required because it 'materially affects the fee estimate,' pickup_at defaults to 30 minutes from now, and delivery_provider defaults to INTERNAL. This extra semantic guidance justifies a score above baseline.

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 opens with a specific verb and resource: 'Check Pizza Hut delivery serviceability and estimated fee for one store and address.' It clearly distinguishes this from ordering or cart tools by stating it 'does not add an item to a cart or place an order,' and it differentiates from store-listing siblings by scoping to a single store and address.

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?

The description gives clear context for when to use the tool: to check delivery serviceability and estimated fee for one store and address. It also states what it does not do (no cart, no order, no payment/account info), but it does not explicitly name alternative tools or provide when-not-to-use guidance beyond those exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools