Skip to main content
Glama
CSOAI-ORG

MEOK Governance Engine MCP

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

which_frameworks_apply

Determine which AI governance frameworks apply to your situation by providing your country, industry, and AI use case. Returns enforcement status and deadlines.

Instructions

Instantly determine which AI governance frameworks apply to your situation.

Input your country, industry, and AI use case. Get back every applicable framework with enforcement status and deadlines.

Behavior: This tool is read-only and stateless — it produces analysis output without modifying any external systems, databases, or files. Safe to call repeatedly with identical inputs (idempotent). Free tier: 10/day rate limit. Pro tier: unlimited. No authentication required for basic usage.

When to use: Use this tool when you need to assess, audit, or verify compliance requirements. Ideal for gap analysis, readiness checks, and generating compliance documentation.

When NOT to use: Do not use as a substitute for qualified legal counsel. This tool provides technical compliance guidance, not legal advice.

Args: country (str): The country to analyze or process. industry (str): The industry to analyze or process. ai_use_case (str): The ai use case to analyze or process. api_key (str): The api key to analyze or process.

Behavioral Transparency: - Side Effects: This tool is read-only and produces no side effects. It does not modify any external state, databases, or files. All output is computed in-memory and returned directly to the caller. - Authentication: No authentication required for basic usage. Pro/Enterprise tiers require a valid MEOK API key passed via the MEOK_API_KEY environment variable. - Rate Limits: Free tier: 10 calls/day. Pro tier: unlimited. Rate limit headers are included in responses (X-RateLimit-Remaining, X-RateLimit-Reset). - Error Handling: Returns structured error objects with 'error' key on failure. Never raises unhandled exceptions. Invalid inputs return descriptive validation errors. - Idempotency: Fully idempotent — calling with the same inputs always produces the same output. Safe to retry on timeout or transient failure. - Data Privacy: No input data is stored, logged, or transmitted to external services. All processing happens locally within the MCP server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryYes
industryNo
ai_use_caseNo
api_keyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description fully covers behavioral traits: read-only, stateless, idempotent, rate limits (10/day free, unlimited pro), authentication (none for basic, API key for pro), error handling (structured errors), and data privacy (no storage/logging).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

Well-organized with sections (Behavior, When to use, Args, Behavioral Transparency), but contains redundancy (e.g., 'read-only' repeated twice) and verbose lists. Could be shortened by 30-40% without losing key details.

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?

Given no annotations and 4 params (1 required), the description thoroughly covers behavior, limitations, authentication, rate limits, error handling, idempotency, and privacy. Output schema exists, so return values need no explanation. Highly complete for the tool's complexity.

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 has 0% parameter descriptions. The 'Args' section adds brief descriptions for all 4 parameters (country, industry, ai_use_case, api_key), but they are generic (e.g., 'The country to analyze or process') and lack details on valid values or format. Partially compensates but not highly informative.

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 determines applicable AI governance frameworks based on country, industry, and use case. It distinguishes itself from sibling tools like compliance_cost_estimator and full_governance_report by focusing on framework identification.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'When to use' and 'When NOT to use' sections provide clear guidance on appropriate usage for compliance assessment and warn against replacing legal counsel. Also specifies rate limits and authentication requirements.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CSOAI-ORG/meok-governance-engine-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server