@striderlabs/mcp-starbucks

get_item_details

Retrieve complete details for a Starbucks menu item, including available customization options like size, milk type, syrups, shots, and temperature for precise drink configuration.

Instructions

Get full details for a menu item including all available customization options (size, milk type, syrups, shots, temperature, etc.).

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": {
      "itemId": "<itemId>"
    },
    "name": "get_item_details"
  }
}

Input Schema

Name	Required	Description	Default
`itemId`	Yes	Item ID from search_menu results (e.g., 'hot-latte', 'cold-brew', 'frap-mocha')

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It mentions that details include customization options but does not specify exact return fields (e.g., price, category) or behavior (e.g., error handling, data freshness). Adequate but lacks specificity.

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?

Single sentence, no fluff. Efficiently communicates purpose and scope.

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

Completeness3/5

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

Even without output schema, the description should more thoroughly explain what 'full details' includes (e.g., price, availability) and clarify that this is pre-customization. Sibling tool customize_item implies further steps, but description does not connect the workflow.

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% with a clear description for itemId. The description adds context about customization options but does not add meaningful information beyond what the schema 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?

Description clearly states it retrieves full details for a menu item, listing customization options. It distinguishes from sibling tools like search_menu (which lists items) and customize_item (which modifies).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Usage is implied (use after search_menu to get details before customizing), but no explicit when-to-use or when-not-to-use guidance is provided. Does not mention alternatives or prerequisites.

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

Deploy Server