Skip to main content
Glama
markswendsen-code

@striderlabs/mcp-shakeshack

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_menuB

Get the Shake Shack menu. Can return all categories or a specific category.

search_menuC

Search the Shake Shack menu for items matching a query.

find_locationsB

Find Shake Shack restaurant locations. Can search by city, state, or keyword.

get_location_detailsC

Get detailed information about a specific Shake Shack location by ID.

get_nutrition_infoB

Get nutritional information and allergen details for Shake Shack menu items.

get_featured_itemsB

Get current featured, seasonal, or limited-time menu items at Shake Shack.

get_ordering_infoB

Get information about how to order at Shake Shack (app, kiosk, online, etc.).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 7 tools

Disambiguation5/5

Each tool has a clearly distinct purpose with no overlap: find_locations (geographic search), get_featured_items (special menu items), get_location_details (specific location info), get_menu (full menu), get_nutrition_info (nutritional data), get_ordering_info (ordering methods), and search_menu (menu item search). The descriptions reinforce these distinct functions, making tool selection unambiguous.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern using snake_case: find_locations, get_featured_items, get_location_details, get_menu, get_nutrition_info, get_ordering_info, and search_menu. The verbs 'find', 'get', and 'search' are appropriately used for their respective actions, creating a predictable and readable naming convention throughout.

Tool Count5/5

With 7 tools, the server is well-scoped for its restaurant information domain. Each tool serves a clear purpose (location discovery, menu access, nutrition details, ordering info), and none feel redundant or unnecessary. This count aligns well with typical MCP server ranges (3-15 tools) for focused functionality.

Completeness4/5

The toolset provides comprehensive coverage for accessing Shake Shack information: locations (find/details), menu (full/featured/search), nutrition, and ordering methods. A minor gap exists in the lack of tools for actual ordering or transaction processing, but given the server's apparent informational focus, this is reasonable. The surface supports common agent workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues