Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

kfc_promotions

Fetch a KFC store's current public deals and offers, including redemption codes, by store number. Returns an empty list when no promotions are active.

Instructions

Get one KFC restaurant's current public promotions. Returns one restaurant's current public promotions -- current deals and offers KFC's storefront marks as public, with each promotion's id, internal and display name, description, whether it applies automatically, and active redemption codes when KFC exposes them. The returned codes can be passed to kfc-promotion. A store with no active public promotions returns an empty list rather than an error.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "store_number": "<store_number>"
    },
    "name": "kfc_promotions"
  }
}

Input Schema

NameRequiredDescriptionDefault
store_numberYesKFC's alphanumeric store number, from /kfc/stores or /kfc/nearby

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description covers important behavior: it returns only public promotions, includes active codes when exposed, and returns an empty list for stores with no promotions instead of error. This is valuable context beyond the schema, though it doesn't mention data source freshness or pagination (but likely not needed).

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 concise, packed with information without redundancy. It efficiently states purpose, return fields, and edge case behavior in about 3 sentences, front-loading the core purpose.

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 tool is simple (1 param) with a rich description covering return content and edge cases. No output schema, but the description lists return fields. Minor gap: does not clarify if store_number refers to a specific region or global, but that is minor.

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 description coverage is 100%: it explains store_number is alphanumeric and from /kfc/stores or /kfc/nearby. The description does not add extra meaning to the parameter beyond that, but baseline is 3 given high schema coverage.

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 retrieves one restaurant's current public promotions, listing specific fields returned (id, names, description, auto-apply, codes). The verb 'Get' and resource 'KFC restaurant promotions' are explicitchers.

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 implies usage: when you need current public promotions for a specific store. It references the store_number parameter and where to find it. It does not explicitly state when not to use it, but in this context where siblings are other domains, the purpose is clear enough.

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