Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kfc_nearby

Locate KFC restaurants near any latitude/longitude, sorted by distance. Filter by order channel such as drive-thru or delivery and get addresses, phone numbers, and online ordering status.

Instructions

Find KFC restaurants near a location. Returns KFC restaurants near a latitude/longitude, nearest first. A coordinate with no nearby KFC returns an empty list rather than an error. Each restaurant carries its store number, full address with coordinates, phone, whether it currently accepts online orders, its timezone, and its distance from the search point in miles. occasion restricts results to restaurants that offer a given order channel (e.g. only drive-thru locations).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
latitudeYesSearch center latitude
occasionNoRestrict to restaurants offering this order channel
longitudeYesSearch center longitude
max_resultsNoMaximum restaurants to return, 1-50 (default 20)
radius_milesNoSearch radius in miles, 0.1-100 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / occasion / enum
      Added value: +[
+  "DELIVERY",
+  "CARRYOUT",
+  "DINE_IN",
+  "DRIVE_THRU",
+  "CATERING_CARRYOUT"
+]
  2. Addedv1.16.2

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It covers several key behaviors: empty list for no nearby KFC, nearest-first ordering, and the specific fields returned. It also explains the occasion filter. However, it does not explicitly state that the operation is read-only or describe any potential side effects, but for a search tool this omission is minor.

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 concise but somewhat repetitive. The first sentence 'Find KFC restaurants near a location' duplicates the second sentence 'Returns KFC restaurants near a latitude/longitude'. The field list is long but could be condensed. Overall, it is not overly padded, but could be trimmed for better structure.

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?

The description covers the core aspects: purpose, input, edge case (empty list), return fields, and the occasion filter. It doesn't mention pagination or defaults, but those are present in the schema. Given the simplicity of a nearby-search tool, it is fairly complete and should allow an agent to call it correctly.

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% since every parameter has a description. The baseline is therefore 3. The description adds extra meaning for the occasion parameter by explaining it restricts results to order channels and giving an example. It does not add significant detail for latitude, longitude, max_results, or radius_miles beyond the schema, so the description adds only marginal value.

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 clearly states the tool's purpose: finding KFC restaurants near a location. It specifies the input (latitude/longitude), output behavior (nearest first), and includes distinguishing details like empty-list handling and the read-only list of fields returned. This makes it easy to understand what the tool does and how it differs from a generic search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternative tools, such as kfc_store or kfc_stores. It does not mention any excluded conditions or when to prefer another tool. The only context is that it returns nearby restaurants, but there is no explicit routing to alternatives.

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