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

@striderlabs/mcp-chickfila

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_nutrition

Look up nutrition information for a specific Chick-fil-A menu item. Provide the item name to receive calories, macronutrients, and allergen details.

Instructions

Get detailed nutrition information for a specific Chick-fil-A menu item.

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": {
      "item_name": "<item_name>"
    },
    "name": "get_nutrition"
  }
}

Input Schema

NameRequiredDescriptionDefault
item_nameYesName of the menu item, e.g. "Spicy Deluxe Sandwich", "Waffle Potato Fries"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior2/5

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

Without annotations, the description carries the full burden of behavioral disclosure. It does not state whether authentication is needed, what exactly 'detailed nutrition information' includes, what happens if the item is not found, or any side effects. The word 'Get' implies a read operation, but no further behavioral context is provided.

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, clear sentence with no unnecessary words. It is front-loaded with the action and resource, making it easy to understand quickly.

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?

Given there is no output schema and no annotations, the description should explain what 'detailed nutrition information' returns and any failure modes. It does not. The single-parameter schema is well covered, but the tool is underspecified for a complete understanding of invocation and expected result.

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% for the single parameter item_name, with a clear description and examples. The tool description adds no additional meaning beyond the schema, so the baseline of 3 applies.

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 action ('Get') and resource ('detailed nutrition information for a specific Chick-fil-A menu item'). It is specific and distinct from sibling tools like search_menu, which would focus on menu items rather than nutrition details.

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

Usage Guidelines3/5

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

The usage context is implied: one would use this tool when needing nutrition information for a menu item. However, there is no explicit guidance on when to use it versus alternatives, nor any mention of exclusions or prerequisites.

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