Crawlora MCP

wendys_item

Read-only

Fetch a Wendy's menu item or combo with price, calories, size variants, allergens, and combo slot composition. Use wendys_menu to browse the menu or wendys_nutrition for the full nutrition panel.

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_item"
  }
}

Input Schema

Name	Required	Description	Default
`item`	Yes	Required. Item slug from /wendys/menu's items[].slug.
`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 7, 2026

TDQS

A4.3/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) with no contradiction. The description adds useful context about content scope (size variants, allergens, combo slot composition), which helps an agent know what a single-item fetch returns, though it says nothing about auth, rate limits, or error behavior.

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, zero waste, and front-loaded: the action and returned fields come first, then the sibling routing. Every clause earns its place.

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

Completeness5/5

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

An output schema exists so return values need not be re-explained, and annotations cover the safety profile. Purpose, content scope, prerequisites (implied via slug sources in schema), and sibling routing are all present, leaving nothing an agent needs 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?

Both parameters are 100% documented in the schema (item is 'Item slug from /wendys/menu's items[].slug' and category is 'Category slug from /wendys/categories'), so the baseline is 3. The description adds no additional meaning about the two slugs beyond what structured data already provides.

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 ('Fetch') and resource ('a Wendy's menu item or combo') and enumerates the returned content (price, calories, size variants, allergens, combo slot composition). It explicitly names the sibling tools it is not, so an agent can distinguish it from wendys_menu and wendys_nutrition 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?

It names two alternatives and their selecting conditions ('Use wendys_menu to browse the menu or wendys_nutrition for the full nutrition panel'). That is clear routing guidance, though it stops short of stating when-not-to-use this tool (e.g. for browsing or searching).

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.