Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wendys_menu

List all items from one Wendy's menu category by slug, returning names, IDs, displayed prices, calories, combo/LTO flags, and required customization.

Instructions

List one Wendy's menu category's items. Returns every item in one category of Wendy's national menu: id, name, slug, Wendy's own displayed price and calorie strings, whether it is a combo (its GET /wendys/item response returns combo_slots instead of components/variants), a limited-time-offer flag, and whether it has required customization (e.g. a salad's dressing choice). Category slugs come from GET /wendys/categories.

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>"
    },
    "name": "wendys_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
categoryYesCategory slug from /wendys/categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4/5.0
Behavior3/5

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

Since no annotations are provided, the description carries the burden. It discloses the return type (list of items with specific fields), and notes subtle behavior like combo detection and required customization flag. However, it doesn't mention pagination, potential errors, or whether the list is exhaustive per category. It's moderately transparent but not exhaustive.

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 (~3 sentences) but information-dense. It front-loads the primary purpose and then details the output in compact list form. No fluff, and it efficiently uses parentheses for clarifications.

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?

Given the tool's simplicity (one parameter, no output schema), the description covers the essential usage information: what it returns, how to get the category slug, and special cases. It lacks details on edge cases (e.g., invalid category slug) but that's minor for a listing tool.

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% (one parameter 'category' described as 'Category slug from /wendys/categories'). The description reiterates this but adds a bit more: explicitly linking to the categories endpoint. Since the schema already covers the parameter, the baseline is 3, and the description adds minimal extra semantics beyond that.

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 purpose: list items in one Wendy's menu category, with specific detail on what data is returned. It distinguishes itself from siblings like wendys_categories and wendys_item by focusing on category listing, and specifically references the sibling category tool for input.

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 gives clear guidance on the input parameter (category slug from /wendys/categories), which effectively tells the agent when to use this tool (after fetching categories). However, it does not explicitly state when not to use it or mention alternatives like wendys_item for individual item details, though the context implies the distinction.

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