Skip to main content
Glama

digital-compass-mcp

by eu.madeinro

List covered situations

compass_list_situations
Read-onlyIdempotent

All digital-crisis situations (reactive playbooks: fake link, hacked account, online scam...) and prevention guides covered by Digital Compass, with slugs for compass_get_content. Public Romanian guide, plain language, content in 9 languages. Optional filters: categorie (use case) and audienta (individ/organizatie).

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
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.

TDQS

A4.6/5.0
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds valuable context: public Romanian guide, plain language, content in 9 languages, and per-language anchoring details. 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.

Conciseness4/5

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

The description is front-loaded with key information and is relatively concise. It could be slightly shorter, but it is well-structured and avoids verbosity.

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?

Even without an output schema, the description indicates that the result includes slugs for use with compass_get_content, covering essential behavior. It also explains language anchoring and audience filters, making it complete for a list tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions. The description adds distinction between playbook and guide categories for the categorie parameter, which is not in the schema. This adds meaning beyond the schema.

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 explicitly states it lists digital-crisis situations and prevention guides, mentioning specific use cases and the purpose of providing slugs for another tool. It clearly distinguishes from siblings like compass_get_content.

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 implies usage for obtaining a list of situations with slugs for further retrieval, and mentions optional filters. However, it does not explicitly state when to use vs alternatives like compass_find_playbook.

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
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose: finding playbooks, checking freshness, retrieving content, listing situations, and getting reporting channels. There is no overlap or ambiguity.

Naming Consistency4/5

Most tools follow a consistent 'compass_verb_noun' pattern (e.g., compass_find_playbook, compass_get_content), but compass_freshness uses a noun instead of a verb, causing a minor inconsistency.

Tool Count5/5

With exactly 5 tools, the set is well-scoped for a digital safety guidance server, covering searching, listing, retrieving content, checking freshness, and getting reporting channels without being too sparse or bloated.

Completeness5/5

The tool set provides a comprehensive coverage for the domain: listing all situations, searching by user description, retrieving full content, checking content freshness, and obtaining reporting channels. No obvious gaps for a read-only repository.

Resources