operandi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| identify_applianceA | Resolve which appliance an agent/robot is looking at, from observed text or panel labels, to an OPERANDI catalog object. Call this first, then get_operation_package with the returned slug. Returns ranked matches with confidence. |
| get_operation_packageA | Get the robot-executable operation package for an appliance: model-exact ordered procedures, a control map with grounding (where each control is + how it is actuated), per-step verification signals, a recovery state machine, and a safety envelope (hazards / interlocks / never-do). This is the grounded knowledge a general model hallucinates without. Optionally target one procedure (e.g. 'defrost'). |
| list_appliancesB | Browse the appliances OPERANDI can operate, optionally filtered by category. |
| find_by_capabilityA | Find appliances by what they DO (e.g. 'heat', 'wash', 'brew', 'defrost') — useful when an agent has a goal but not a specific model in mind. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: find by capability, identify from observation, get operation package, and list all appliances. There is no overlap; the descriptions clearly differentiate them.
All names use snake_case and are descriptive, but 'find_by_capability' breaks the verb_noun pattern used by the others (identify, get, list). This is a minor inconsistency.
With 4 tools, the server covers the essential workflow (browse, search, identify, retrieve details) for its niche domain. It is slightly minimal but well-scoped, so score 4.
The set covers browsing, searching by capability, identification from observation, and retrieving detailed operation packages. Missing features like direct model lookup or procedure listing are minor gaps.