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

@striderlabs/mcp-starbucks

by markswendsen-code
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

select_store

Select a Starbucks store as the pickup location for a mobile order. Must be called before placing an order.

Instructions

Select the Starbucks store for mobile pickup. Must be called before placing an order.

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": {
      "storeId": "<storeId>"
    },
    "name": "select_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
storeIdYesStore ID from get_nearby_stores results

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

No annotations provided; description implies a mutating operation but does not detail behavioral traits like idempotency or side effects beyond the obvious.

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, clear and front-loaded with no extraneous information.

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?

All necessary context provided for a simple tool with one parameter and no output schema; the description is sufficient for correct invocation.

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?

Parameter storeId has schema coverage 100% and description adds source context ('from get_nearby_stores results'), enhancing meaning beyond the schema alone.

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 ('select store for mobile pickup') and resource ('Starbucks store'), distinguishing it from sibling tools like get_nearby_stores and place_order.

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?

Explicitly states when to use ('Must be called before placing an order'), but lacks explicit when-not-to-use or alternatives, though context from siblings implies it.

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