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

@striderlabs/mcp-starbucks

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

place_order

Submit your cart as a mobile pickup order. Preview by setting confirm=false, then place with confirm=true.

Instructions

Submit your cart as a mobile pickup order at the selected store. Set confirm=false to preview first, confirm=true to actually place it. Requires being logged in.

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

Input Schema

NameRequiredDescriptionDefault
confirmNoSet true to place the order, false to preview only (default: false)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, the description must disclose behavior. It states the login requirement and differentiates between preview and placement. However, it does not mention side effects (e.g., cart clearing), rate limits, or irreversibility. Adequate but not exhaustive.

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?

Two sentences, 28 words, front-loaded with the main purpose. Every sentence provides necessary information. 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 parameter and no output schema, the description covers the essential purpose, parameter usage, and prerequisite. It could mention that items must be in cart, but it's largely complete.

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 repeats the schema's explanation of the confirm parameter without adding new information. It adds no extra context beyond the schema, so baseline score of 3 is appropriate.

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: 'Submit your cart as a mobile pickup order at the selected store.' It specifies the verb (submit) and resource (cart/pickup order), and distinguishes from sibling tools like add_to_cart and view_cart.

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

Usage Guidelines4/5

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

The description provides clear usage guidance: set confirm=false to preview, confirm=true to place, and requires being logged in. It does not explicitly state when not to use or list alternatives, but the prerequisite is clear.

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