Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

wendys_store_menu

Retrieve a specific Wendy's store's full menu with real local prices and store-specific promotions using its store ID.

Instructions

Get one Wendy's restaurant's full priced/offered menu. Returns one restaurant's own priced, offered item list -- real local pricing (including full combo bundle prices, which GET /wendys/item deliberately does not compute, since a combo's own price varies by what's chosen in each slot) and any store-specific promotional items, rather than Wendy's own generic/average national-menu listing (GET /wendys/menu, /wendys/item). A request with just a store id returns real data, no session or account required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
store_idYesNumeric store id, e.g. from /wendys/nearby's stores[].store_id or /wendys/restaurant's store_id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.2

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does well: it discloses that no session or account is required, that combos are priced here but deliberately not at /wendys/item, and that results are store-specific. It does not describe return shape, pagination, or error behavior, so it stops short of full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first sentence and every sentence adds information. The second sentence is long and parenthetical-heavy (the combo-slot explanation), which slightly hurts scannability but the detail is substantive.

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?

Covers purpose, differentiation, auth-free access, and the type of content returned (priced item list, promos, combo prices). With no output schema and no annotations, some return-shape detail would help, but the description is otherwise sufficient for calling 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?

Schema coverage is 100%, so store_id's format and sourcing are already documented in the schema. The description only reinforces that a single store id returns real data, adding no new syntax or constraint 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?

States a specific verb and resource ('Get one Wendy's restaurant's full priced/offered menu') and explicitly distinguishes it from the generic national listing at /wendys/menu and /wendys/item. An agent can tell this apart from its Wendy's siblings without reading 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 Guidelines5/5

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

Names the alternative endpoints (GET /wendys/menu, /wendys/item) and the condition that selects this one: real local pricing, computed combo bundle prices, and store-specific promotions versus generic/average national listings. It also clarifies that a bare store id suffices with no session or account.

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