Crawlora MCP

wendys_nutrition

Read-only

Fetch the full Wendy's nutrition panel with real-number values, vitamins, minerals, and declared allergens; combo totals use each slot's default choice. Use wendys_item for modifiers or wendys_menu to browse.

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": {
      "category": "<category>",
      "item": "<item>"
    },
    "name": "wendys_nutrition"
  }
}

Input Schema

Name	Required	Description	Default
`item`	Yes	Required. Item slug from /wendys/menu's items[].slug. A combo slug is accepted -- see is_combo/combo_selections on the response.
`category`	Yes	Required. Category slug from /wendys/categories.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's job is additive context. It delivers that by disclosing the payload character ("real-number values, vitamins, minerals, and declared allergens") and a genuine behavioral nuance: combo totals resolve to each slot's default choice.

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?

Two sentences, both earning their place: the first defines the payload and a combo caveat, the second handles routing. No filler and the core purpose is front-loaded.

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?

With an output schema present, return values need not be described, and both params are fully covered by the schema. The description adds useful combo semantics and sibling routing; only a note on prerequisites (resolving slugs via /wendys/menu first) is missing.

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% — both params are documented inline with their source endpoints (/wendys/menu items[].slug, /wendys/categories). The description adds no additional parameter syntax or format detail beyond the combo default note, so the baseline 3 is appropriate.

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?

States a specific verb and resource ("Fetch the full Wendy's nutrition panel") and immediately names the two siblings it is not: wendys_item for modifiers, wendys_menu to browse. An agent can distinguish this from adjacent Wendy's tools without opening any schema.

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?

Explicitly routes to alternatives: "Use wendys_item for modifiers or wendys_menu to browse." That is clear positive guidance, though it doesn't state a negative condition (e.g., when NOT to call it, or that it should be called after resolving a slug).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?