Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kfc_delivery_estimate

Check if a KFC store delivers to an address and get the estimated delivery fee with pickup/dropoff times, using the same checkout estimate as KFC's site.

Instructions

Check KFC delivery serviceability and estimated fee for one store and address. Checks whether a KFC 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 KFC'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: the delivery provider not enabled at this store, the address being outside the delivery zone, or the delivery marketplace itself reporting the store temporarily inactive. order_subtotal materially affects the fee estimate (KFC's own fee schedules can vary by order size), 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_numberYesKFC's alphanumeric store number, from /kfc/stores or /kfc/nearby
order_subtotalYesOrder subtotal before fees, in dollars
delivery_providerNoDelivery provider to check (default DOORDASH)

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, the description carries the full burden and does an excellent job: it discloses the tool is read-only (no cart, order, payment), defines the exact semantics of serviceable (true only on real estimate; false with reason for provider not enabled, outside zone, or marketplace inactive), and explains why order_subtotal is required and pickup_at defaults. This goes well beyond typical descriptions.

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 front-loads the purpose and then adds only value-bearing sentences: read-only trait, serviceable semantics, order_subtotal rationale, pickup_at default. No filler, each sentence earns its place, and length is justified by the tool's complexity.

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?

With no output schema and no annotations, the description explains what the tool returns (fee breakdown, pickup/dropoff time, serviceable flag and reason semantics) and essential input behaviors. It covers the critical aspects needed to select and invoke correctly, leaving nothing important missing.

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 baseline is 3. The description adds meaning beyond the schema by explaining why order_subtotal is required (fee schedules vary by order size) and what pickup_at's default means ('order now' style estimate). It doesn't add semantic detail to the other parameters, but the ones that need it are covered.

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?

First sentence states a specific verb and resource ('Check KFC delivery serviceability and estimated fee for one store and address'), and further clarifies scope and what it doesn't do (does not add to cart, place order, take payment). This distinguishes it from ordering-related tools and from other KFC tools like kfc_nearby or kfc_menu.

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?

States the tool checks one store and address, implying it's for single-store estimates, but does not explicitly name sibling alternatives or exclusion conditions. The read-only note clarifies when not to use it (when placing an order), but no explicit alternative is named. Clear context but no explicit 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