franchisedata-mcp

Real-Time Starbucks Operating Status

starbucks_store_status

Read-onlyIdempotent

Retrieve live open/closed status and weekly operating schedule for a specific Starbucks store to check current hours or availability.

Instructions

PAID ($0.002). Retrieve live operating status, weekly schedule, and current open/closed state for a specific Starbucks store. Atomically debits $0.002 from prepaid balance. Requires 'fc_live_...' API key. If 'store_id' is omitted, defaults to the first indexed store. Returns 404 if store is not found, 402 if balance insufficient. WHEN TO USE: Use to verify whether an individual Starbucks store is currently open or to view its operating schedule. WHEN NOT TO USE: Do not use for fleet-wide location discovery (use 'franchise_search_near' or 'fetch_franchise_data'). ALTERNATIVES: Use 'franchise_search_near' for finding open stores near coordinates; use 'track_brand_changes' for permanent closures.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`store_id`	No	Optional Starbucks store identifier or store number (e.g. '1033083', 'loc_starbucks_1033083'). If omitted, inspects the first indexed store.

Output Schema

TableJSON Schema

Name	Required	Description
`city`	No	City
`name`	No	Store location name
`hours`	No	Weekly operating hours by daypart and weekday
`state`	No	State postal abbreviation
`status`	Yes	Current operating status ('Open' or 'Closed')
`address`	No	Street address
`store_number`	Yes	Store identifier number
`balance_remaining_usd`	Yes	Remaining API credit balance in USD

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv1.0.1Oct 6, 2026

changedInput schema / properties / store_id / description

Previous value: -"Store ID or store number, e.g. 'STA-1002'"New value: +"Optional Starbucks store identifier or store number (e.g. '1033083', 'loc_starbucks_1033083'). If omitted, inspects the first indexed store."

removedInput schema / required
```
Removed value: -[
-  "store_id"
-]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "address": {
+      "description": "Street address",
+      "type": "string"
+    },
+    "balance_remaining_usd": {
+      "description": "Remaining API credit balance in USD",
+      "type": "string"
+    },
+    "city": {
+      "description": "City",
+      "type": "string"
+    },
+    "hours": {
+      "description": "Weekly operating hours by daypart and weekday",
+      "type": "object"
+    },
+    "name": {
+      "description": "Store location name",
+      "type": "string"
+    },
+    "state": {
+      "description": "State postal abbreviation",
+      "type": "string"
+    },
+    "status": {
+      "description": "Current operating status ('Open' or 'Closed')",
+      "type": "string"
+    },
+    "store_number": {
+      "description": "Store identifier number",
+      "type": "string"
+    }
+  },
+  "required": [
+    "store_number",
+    "status",
+    "balance_remaining_usd"
+  ],
+  "type": "object"
+}

First observedv1.0.0Oct 1, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/openWorld=false, and the description adds substantial context beyond them: the $0.002 atomic debit from prepaid balance, the required 'fc_live_...' API key, and the 404/402 error semantics. This is exactly the extra behavioral layer the dimension rewards.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core capability, cost, and auth before the WHEN TO USE/WHEN NOT blocks. Dense but nearly every sentence earns its place; minor redundancy in stating the paid cost in both the leading tag and the body.

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?

For a single-optional-param read tool with an output schema, the description covers everything an agent needs: cost, auth requirement, default behavior, and error outcomes. Return-value details are correctly left to the output schema.

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 there is only one optional parameter, so the schema already documents the store_id format and default behavior. The description restates the default-to-first-indexed-store behavior without adding format or syntax detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb+resource ('Retrieve live operating status, weekly schedule, and current open/closed state for a specific Starbucks store') with a clearly bounded scope. It is instantly distinguishable from siblings like franchise_search_near or track_brand_changes, which it names explicitly.

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

Usage Guidelines5/5

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

Provides explicit WHEN TO USE ('verify whether an individual store is currently open or view its schedule'), WHEN NOT TO USE (not for fleet-wide discovery), and ALTERNATIVES naming two specific sibling tools with the conditions that select them. Nothing is left to inference.

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

Deploy Server