Skip to main content
Glama
CSOAI-ORG

MEOK Fria Generator MCP

pricing

Check the current rates for using the MEOK FRIA Generator to understand usage fees.

Instructions

Pricing for MEOK FRIA Generator.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The pricing() function is the MCP tool handler decorated with @mcp.tool(). It returns pricing tiers (free, pro, enterprise, bespoke) as a dictionary with features, price, and contact/purchase links.
    @mcp.tool()
    def pricing() -> dict[str, Any]:
        """Pricing for MEOK FRIA Generator."""
        return {
            "free_tier": {
                "price": "£0",
                "features": [
                    "All FRIA generation tools",
                    "Public attestation API (shared HMAC issuer)",
                    "MIT-licensed source code",
                    "EDPB DPIA crosswalk included",
                ],
            },
            "pro": {
                "price": "£79/mo",
                "features": [
                    "Free tier + your own HMAC signing key",
                    "Custom verify domain (your-firm.com/verify)",
                    "Email support",
                    "FRIA template versioning + diff tracking",
                ],
            },
            "enterprise": {
                "price": "£1,499/mo",
                "features": [
                    "Pro tier + multi-deployment FRIA management for groups",
                    "SLA on attestation API (99.9%)",
                    "Direct slack/teams support channel",
                    "Reseller white-label for compliance consultancies",
                ],
                "fit": "Public-sector deployers with multiple Annex III systems; consultancies "
                "running concurrent FRIA engagements",
            },
            "bespoke": {
                "price": "from £5,000",
                "features": [
                    "Self-hosted attestation API on your infrastructure",
                    "GRC stack integrations (Archer, ServiceNow, OneTrust)",
                    "On-site FRIA workshop (1 day)",
                ],
            },
            "purchase": "https://meok.ai/pricing",
            "contact": "nicholas@csoai.org",
        }
  • The tool is registered via the @mcp.tool() decorator on line 358, which registers the pricing function with the FastMCP server instance (line 25: mcp = FastMCP("meok-fria-generator"))
    @mcp.tool()
  • The return type is dict[str, Any] with no input parameters. The output schema is implicit in the returned dictionary structure with keys: free_tier, pro, enterprise, bespoke, purchase, contact.
    return {
        "free_tier": {
            "price": "£0",
            "features": [
                "All FRIA generation tools",
                "Public attestation API (shared HMAC issuer)",
                "MIT-licensed source code",
                "EDPB DPIA crosswalk included",
            ],
        },
        "pro": {
            "price": "£79/mo",
            "features": [
                "Free tier + your own HMAC signing key",
                "Custom verify domain (your-firm.com/verify)",
                "Email support",
                "FRIA template versioning + diff tracking",
            ],
        },
        "enterprise": {
            "price": "£1,499/mo",
            "features": [
                "Pro tier + multi-deployment FRIA management for groups",
                "SLA on attestation API (99.9%)",
                "Direct slack/teams support channel",
                "Reseller white-label for compliance consultancies",
            ],
            "fit": "Public-sector deployers with multiple Annex III systems; consultancies "
            "running concurrent FRIA engagements",
        },
        "bespoke": {
            "price": "from £5,000",
            "features": [
                "Self-hosted attestation API on your infrastructure",
                "GRC stack integrations (Archer, ServiceNow, OneTrust)",
                "On-site FRIA workshop (1 day)",
            ],
        },
        "purchase": "https://meok.ai/pricing",
        "contact": "nicholas@csoai.org",
    }
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It implies a read operation but does not disclose if the tool is idempotent, requires authentication, or has side effects. The single sentence fails to provide behavioral context beyond a vague topic.

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?

The description is a single, short sentence that is front-loaded and contains no extraneous words. It is appropriately concise for a tool with no parameters.

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

Completeness3/5

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

For a simple tool with no parameters and an output schema, the description is somewhat incomplete. It hints at pricing but does not describe the output format or content. While it meets minimum viability, it could better indicate what the agent can expect.

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?

The tool has 0 parameters, so schema coverage is 100%. According to guidelines, baseline is 4 for zero parameters. The description adds minimal context by specifying the domain (pricing for MEOK FRIA Generator), which is acceptable given no parameters to explain.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Pricing for MEOK FRIA Generator' is a noun phrase lacking a verb and does not specify the action (e.g., get, calculate). It vaguely indicates the tool provides pricing information but does not differentiate itself from sibling tools like 'generate_fria_template' or 'is_fria_required'.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent with no decision support.

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-fria-generator-mcp'

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