Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kfc_stores

Locate KFC restaurants using city, state, postal code, name, franchise code, or store number. Returns full address, phone, coordinates, online-order availability, 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 -- confirmed live that 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.1/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It discloses the mandatory filter requirement, the intentional lack of an unfiltered endpoint, the fields each restaurant carries, and the behavior of appear_in_store_results including a live confirmation that raw filters can return administrative entries. This is thorough and goes well beyond a minimal statement.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is rich but somewhat redundant: the first two sentences essentially repeat the same filter list. It is front-loaded with the purpose but could be tightened. Despite the redundancy, the additional details about required filters, return fields, and default behavior are valuable, so it is not overly verbose.

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 tool's complexity (9 parameters, no output schema), the description is quite complete. It covers the mandatory filter constraint, the key return fields, and the behavior of appear_in_store_results. It does not explain sort or max_results, but those are documented in the schema virtually. The cross-reference to other endpoints is a useful contextual touch.

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?

The input schema has 100% description coverage, so the baseline is 3. The description adds meaning by clarifying that at least one filter is required (schema does not mark any required), explaining the purpose of store_number as the key for other endpoints, and providing nuance about appear_in_store_results with a live-tested caveat. This adds value beyond 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?

The description clearly states the tool searches for KFC restaurants by various filters, naming the specific filters (city, state, postal code, name, franchise code, store number) and the output fields. It does not explicitly differentiate from sibling tools like kfc_nearby or kfc_store, but the parameter list and search semantics make the purpose unambiguous.

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 usage context: at least one filter is required, explains why (unfiltered call would enumerate all US restaurants), and details the default behavior of appear_in_store_results with a live confirmation. It does not explicitly state when to use this tool over siblings, but the cross-reference to /kfc/menu and /kfc/promotions provides indirect guidance on when this tool is needed.

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