Skip to main content
Glama

digital-compass-mcp

by eu.madeinro
OverviewDiscussionsAdmin

Find the right playbook for a situation

compass_find_playbook
Read-onlyIdempotent

Matches the situation in the user's own words ("I clicked a link and it asked for my card") against the covered situations. Deterministic keyword matching (title, situation, summary), not guessing. Returns the best 3 matches with a score.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
langNoContent language (ro = original; en/hu anchored in Romania; pl/cs/sk/it/fr/de anchored in their own countries, with local reporting channels)ro
queryYesThe situation, in the user's own words
audientaNoOptional audience filter: individ (private person) or organizatie (company/team). Content marked "ambele" matches both.
categorieNoOptional use-case category filter. Playbook categories: cumparaturi-bani, conturi-dispozitive, mesaje-apeluri, oameni-manipulare, ai-asistenti. Guide categories: conturi-parole, cumparaturi-plati, dispozitive, email-mesaje, la-birou.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / categorie / description
      Previous value: -"Optional use-case category filter. Playbook categories: cumparaturi-bani, conturi-dispozitive, mesaje-apeluri, oameni-manipulare. Guide categories: conturi-parole, cumparaturi-plati, dispozitive, email-mesaje, la-birou."New value: +"Optional use-case category filter. Playbook categories: cumparaturi-bani, conturi-dispozitive, mesaje-apeluri, oameni-manipulare, ai-asistenti. Guide categories: conturi-parole, cumparaturi-plati, dispozitive, email-mesaje, la-birou."
    • changedInput schema / properties / categorie / enum
      Previous value: -[
-  "cumparaturi-bani",
-  "conturi-dispozitive",
-  "mesaje-apeluri",
-  "oameni-manipulare",
-  "conturi-parole",
-  "cumparaturi-plati",
-  "dispozitive",
-  "email-mesaje",
-  "la-birou"
-]New value: +[
+  "cumparaturi-bani",
+  "conturi-dispozitive",
+  "mesaje-apeluri",
+  "oameni-manipulare",
+  "ai-asistenti",
+  "conturi-parole",
+  "cumparaturi-plati",
+  "dispozitive",
+  "email-mesaje",
+  "la-birou"
+]
  2. Changed2 schema fields changed
    • addedInput schema / properties / audienta
      Added value: +{
+  "description": "Optional audience filter: individ (private person) or organizatie (company/team). Content marked \"ambele\" matches both.",
+  "enum": [
+    "individ",
+    "organizatie"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / categorie
      Added value: +{
+  "description": "Optional use-case category filter. Playbook categories: cumparaturi-bani, conturi-dispozitive, mesaje-apeluri, oameni-manipulare. Guide categories: conturi-parole, cumparaturi-plati, dispozitive, email-mesaje, la-birou.",
+  "enum": [
+    "cumparaturi-bani",
+    "conturi-dispozitive",
+    "mesaje-apeluri",
+    "oameni-manipulare",
+    "conturi-parole",
+    "cumparaturi-plati",
+    "dispozitive",
+    "email-mesaje",
+    "la-birou"
+  ],
+  "type": "string"
+}
  3. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Limba conținutului (ro = original; en/hu ancorate în România; pl/cs/sk/it/fr/de ancorate în țările lor, cu canale locale)"New value: +"Content language (ro = original; en/hu anchored in Romania; pl/cs/sk/it/fr/de anchored in their own countries, with local reporting channels)"
    • changedInput schema / properties / query / description
      Previous value: -"Situația, în cuvintele utilizatorului"New value: +"The situation, in the user's own words"
  4. Changed2 schema fields changed
    • changedInput schema / properties / lang / description
      Previous value: -"Limba conținutului (ro = original; en/hu ancorate în România, pl ancorat în Polonia)"New value: +"Limba conținutului (ro = original; en/hu ancorate în România; pl/cs/sk/it/fr/de ancorate în țările lor, cu canale locale)"
    • changedInput schema / properties / lang / enum
      Previous value: -[
-  "ro",
-  "en",
-  "hu",
-  "pl"
-]New value: +[
+  "ro",
+  "en",
+  "hu",
+  "pl",
+  "cs",
+  "sk",
+  "it",
+  "fr",
+  "de"
+]
  5. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark readOnlyHint and idempotentHint. The description adds valuable context: deterministic keyword matching (not guessing), result limit of 3, and scoring. No contradictions with annotations.

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, front-loaded with purpose, no wasted words. Efficiently conveys matching algorithm, constraints, and output format.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers input (query, language, filters) and output (3 best matches with scores). Lacks mention of how scoring works or edge-case handling, but sufficient given no 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 covers 100% of parameters with descriptions. The description does not add per-parameter details but explains overall input-output behavior. Baseline 3 is appropriate as the schema already does heavy lifting.

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 tool matches user's situation description against covered situations using deterministic keyword matching, returning best 3 matches with a score. It distinguishes from sibling tools like compass_list_situations (which lists all situations) and compass_get_content (which retrieves content by ID).

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?

The description explains when to use (user's own words for situation matching) and the deterministic behavior, but does not explicitly exclude scenarios or list alternatives among siblings. The context is clear enough for an agent to infer appropriate use.

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

All digital-compass-mcp toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources