Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

starbucks_menu

Read-only

Browse Starbucks' full menu as a category tree: top-level categories, their child categories, and every product with its product number, form, product type, sizes, default size, availability, and image. Pair a product's product_number and form with starbucks_product for full detail including nutrition. store_number optionally scopes the menu to one store, using a store number from starbucks_stores; a store-scoped menu marks items that store does not carry with availability NotAvailableHere, while the unscoped menu reports everything as Available. market selects which country catalog to return, one of us or ca (default us); the two differ substantially (about 282 US products vs 253 CA, with exclusives on both sides). Only these two markets exist -- every other Starbucks country site runs a different platform.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "starbucks_menu"
  }
}

Input Schema

NameRequiredDescriptionDefault
marketNoStarbucks country site to read. One of: us, ca. Defaults to us. Documented values: us, ca.
store_numberNoStarbucks store number to scope availability to, e.g. 101-54

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / market / description
      Added value: +"Starbucks country site to read. One of: us, ca. Defaults to us. Documented values: us, ca."
    • addedInput schema / properties / store_number / description
      Added value: +"Starbucks store number to scope availability to, e.g. 101-54"
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses non-obvious behavior: the unscoped menu reports everything as Available, while a store-scoped menu marks uncarried items as NotAvailableHere. It also warns that only us and ca exist and that the two catalogs differ substantially (~282 vs ~253 products with exclusives), which materially affects results.

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?

The what-it-returns content is front-loaded and every sentence carries information. The market paragraph is slightly verbose with the product-count aside, but it is defensible because it justifies the parameter's impact rather than padding.

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?

With an output schema present and annotations covering the safety profile, the description still supplies everything else an agent needs: return shape, the sibling it pairs with, store-scoping semantics, and market scope limits. Nothing required to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents both parameters, but the description adds real meaning: it explains the downstream effect of store_number (availability marking logic) and the rationale and magnitude of the market choice. It stops just short of syntax examples for the store_number format, which the schema supplies.

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 opens with a specific verb and resource, 'Browse Starbucks' full menu as a category tree,' and enumerates exactly what the tree contains (categories, child categories, and products with their attributes). It clearly differentiates from siblings like starbucks_product and starbucks_nutrition by naming them and describing the handoff.

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?

It explicitly routes the agent: pair product_number and form with starbucks_product for full detail including nutrition. It also gives the condition for scoping (store_number optionally scopes to one store, sourced from starbucks_stores) and for choosing market. Alternatives and when-to-use are both stated.

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

All Crawlora MCP toolsInspect
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