Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kfc_stores

Search KFC restaurants by city, state, postal code, name, franchise code, or store number and return matching locations with store number, address, phone, online-order status, and timezone.

Instructions

Search KFC restaurants by city, state, postal code, name, franchise code, or store number. Returns KFC restaurants matching a city/state/postal code/name/franchise code/store number filter. At least one filter is required -- an unfiltered call would enumerate every US restaurant in one response, which this endpoint intentionally does not expose. Each restaurant carries its store number (the value /kfc/menu and /kfc/promotions take), full address with coordinates, phone, whether it currently accepts online orders, and its timezone. appear_in_store_results (default true) excludes internal/test records KFC's own storefront does not surface in customer-facing search -- a raw filter can otherwise return non-orderable administrative entries alongside real restaurants.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cityNoRestaurant city
nameNoRestaurant name, partial match
sortNoSort order
stateNoRestaurant state, two-letter code
max_resultsNoMaximum restaurants to return, 1-50 (default 20)
postal_codeNoRestaurant postal code
store_numberNoExact store number
franchise_codeNoExact franchise/operator code
appear_in_store_resultsNoRestrict to restaurants shown in customer-facing search, excluding internal/test entries (default true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / sort / enum
      Added value: +[
+  "store_number_asc",
+  "store_number_desc",
+  "name_asc",
+  "name_desc",
+  "franchise_code_asc",
+  "franchise_code_desc"
+]
  2. Addedv1.16.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden well: it discloses the any-of filter requirement, the intentional avoidance of full enumeration, the returned fields, and why appear_in_store_results defaults to true. It does not cover rate limits or broader pagination behavior beyond the schema's max_results.

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 description is front-loaded and appropriately sized for a 9-parameter search tool with no output schema. The filter list is repeated slightly across the first two sentences, but the remaining sentences add useful return and exclusion context.

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?

Given the rich schema, no annotations, and no output schema, the description is largely complete: it explains the filter requirement, return payload, and the important internal-record exclusion flag. The main missing piece is explicit sibling routing between kfc_stores, kfc_nearby, and kfc_store.

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 is 3, but the description adds meaningful semantics: store_number is the value consumed by /kfc/menu and /kfc/promotions, and appear_in_store_results excludes internal/test records by default. It leaves sort and max_results to the schema.

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?

States a specific verb (search) and resource (KFC restaurants) and enumerates the supported filters. It is clear what the tool does, though it does not explicitly contrast itself with siblings such as kfc_nearby or kfc_store.

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?

Explains that at least one filter is required and why an unfiltered call is rejected, which gives clear usage context. It does not explicitly tell the agent when to choose kfc_nearby or kfc_store instead, so sibling routing is left to inference.

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