Compass DaaS
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COMPASS_API_KEY | Yes | Compass Sandbox or live API key. Required for live tool calls. | |
| COMPASS_BASE_URL | No | Optional Compass API base URL. Defaults to production. |
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 |
|---|---|
| compass_searchA | Search restaurants by natural-language dietary query. Returns ranked results with VeganScore, evidence, and confidence. Conservative: returns "unknown" when evidence is insufficient and does not return certification/free-from facts. |
| compass_enrich_restaurantA | Match a restaurant by name and address, then return Compass enrichment data including VeganScore, vegan dietary profile, and evidence. Does not return certification/free-from facts. Returns "matched: false" with candidates if confidence is below threshold. |
| compass_decide_fitA | Conservative fit decision for a restaurant against a user dietary profile. Returns "fit", "not_fit", or "unknown" with reason codes, evidence, and user wording. Returns "unknown" rather than overclaiming. |
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 3 tools
Each tool has a distinct purpose: decide_fit makes a dietary fit determination, enrich_restaurant returns enrichment data for a specific restaurant, and search allows natural-language queries. There is no overlap or ambiguity.
All tools follow the consistent pattern 'compass_verb_noun' (decide_fit, enrich_restaurant, search). The naming is predictable and uniform.
With only 3 tools, the set is appropriately scoped for the narrow domain of restaurant dietary matching. Each tool is essential and there is no bloat.
The tools cover search, enrichment, and fit decision, which are the core operations for the domain. No obvious gaps exist given the stated purpose of providing dietary data service.