Skip to main content
Glama
Sign In
@striderlabs/mcp-chickfila

@striderlabs/mcp-chickfila

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

place_order

Place a mobile order at a Chick-fil-A location using your location ID and preferred payment method. Requires authentication and items in cart.

Instructions

Place a mobile order at a Chick-fil-A location. Requires authentication and items in cart.

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": {
      "location_id": "<location_id>",
      "payment_method": "<payment_method>"
    },
    "name": "place_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
location_idYesChick-fil-A restaurant location ID
payment_methodYesPayment method to use, e.g. "saved card", "Chick-fil-A One points"
special_instructionsNoOptional special instructions for the order

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of explaining behavioral impact. It mentions authentication and cart items, but fails to disclose that this places a real financial order, charges the payment method, is likely irreversible, or what success/error responses look like. This is a significant gap for a consequential purchase action.

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 a single sentence that front-loads the core action ('Place a mobile order') and then adds two essential prerequisites. Every word earns its place with no fluff or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that triggers a real financial transaction, the description is incomplete. It covers prerequisites but omits key context such as order confirmation behavior, potential failure modes (e.g., invalid payment), and whether the order can be cancelled. The absence of an output schema further increases the need for description-led context, which is not met.

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?

The schema already provides descriptions for 100% of parameters, so the description adds little beyond what is structured. The baseline of 3 applies here; the description does not provide additional syntax or nuance for parameters beyond the schema.

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 states a specific verb ('Place') and resource ('a mobile order at a Chick-fil-A location'), which clearly distinguishes it from sibling tools like add_to_cart and check_order_status. It communicates the core action without requiring the agent to infer from the tool name alone.

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 explicitly lists prerequisites ('Requires authentication and items in cart'), providing clear context for when this tool can be used. It does not explicitly name alternatives or exclusions, but the prerequisites implicitly guide the agent to call this after authentication and cart setup.

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