@striderlabs/mcp-starbucks

get_order_status

Retrieve the preparation status and estimated pickup time for a Starbucks mobile order. Optionally specify an order ID to track a specific order, or check the most recent order.

Instructions

Track the status of a Starbucks mobile order. Shows preparation status and estimated pickup time.

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": "get_order_status"
  }
}

Input Schema

Name	Required	Description	Default
`orderId`	No	Order ID to track. If omitted, shows the most recent order status.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0May 28, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Without annotations, the description bears full burden. It discloses that the tool shows preparation status and pickup time, but does not specify if it's read-only, requires authentication, or any other behavioral traits like rate limits or data freshness.

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 two sentences, front-loading the key purpose and details. Every word earns its place with no fluff.

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?

For a simple tool with one optional parameter and no output schema, the description covers core functionality well. It is missing hints about return format (e.g., plain text vs structured) and preconditions like authentication, but these are minor given the tool's simplicity.

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% and already explains the orderId parameter, including default behavior. The tool description adds no further semantic value beyond what the schema 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?

The description clearly states the tool's purpose: tracking a Starbucks mobile order status, showing preparation status and estimated pickup time. It uses a specific verb-resource pair and distinguishes from siblings like get_order_history or starbucks_status.

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?

The description implies usage for tracking orders but lacks explicit when-to-use or when-not-to-use guidance. No mention of prerequisites like being authenticated or having an order placed, and no alternatives are suggested.

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

Deploy Server