Skip to main content
Glama
Sign In
@striderlabs/mcp-starbucks

@striderlabs/mcp-starbucks

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

reorder_favorite

Recreate your favorite order by loading all items from a past order into your cart. Requires being logged in.

Instructions

Quickly reorder from a past order — loads all items from a previous order back into your cart. Requires being logged in.

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": {
      "orderId": "<orderId>"
    },
    "name": "reorder_favorite"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderIdYesOrder ID from get_order_history to reorder

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It mentions that items are loaded into the cart but does not disclose whether the current cart is cleared, if partial reordering is allowed, or what happens if items are no longer available. This lack of detail limits transparency.

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 with two clear sentences. It starts with the main purpose and adds the key prerequisite, with no wasted words.

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 parameter and no output schema, the description covers the purpose, prerequisite, and parameter source. It is nearly complete, though it could benefit from noting the effect on the existing cart.

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 the description adds that orderId comes from get_order_history. This is helpful but does not add significant new meaning 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?

The description clearly states the action ('reorder from a past order') and the resource ('all items from a previous order back into your cart'). It distinguishes from siblings like add_to_cart by specifying it loads an entire past order, not individual items.

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 notes that login is required, providing some context. However, it does not explicitly state when to use this tool versus alternatives (e.g., add_to_cart for individual items) or when not to use it (e.g., if items are unavailable).

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