Skip to main content
Glama
CSOAI-ORG

MEOK DORA Tlpt Planner MCP

by CSOAI-ORG
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

pricing

Obtain the cost details for the MEOK DORA TLPT Planner to manage your budget.

Instructions

Pricing for MEOK DORA TLPT Planner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • meok_dora_tlpt_planner/server.py:364-404 (handler)
    The `pricing` MCP tool handler function. Returns a dictionary with pricing tiers (free, pro, enterprise, bespoke) and contact/purchase info.
    @mcp.tool()
def pricing() -> dict[str, Any]:
    """Pricing for MEOK DORA TLPT Planner."""
    return {
        "free_tier": {
            "price": "£0",
            "features": [
                "All scope/TTI/remediation tools above",
                "Public attestation API (shared HMAC issuer)",
                "MIT-licensed source code",
            ],
        },
        "pro": {
            "price": "£79/mo",
            "features": [
                "Free tier + your own HMAC signing key",
                "Custom attestation domain (your-firm.com/verify)",
                "Email support",
            ],
        },
        "enterprise": {
            "price": "£1,499/mo",
            "features": [
                "Pro tier + multi-BU separation for group-level TLPT coordination",
                "SLA on attestation API (99.9%)",
                "Direct slack/teams support channel",
                "White-label for resellers (consultancies)",
            ],
            "fit": "Significant/systemic financial entities with concurrent TLPT engagements across BUs",
        },
        "bespoke": {
            "price": "from £5,000",
            "features": [
                "Self-hosted attestation API on your infrastructure",
                "Custom integrations with GRC stack (Archer, ServiceNow, etc.)",
                "On-site white-team training (2 days)",
            ],
        },
        "purchase": "https://meok.ai/pricing",
        "contact": "nicholas@csoai.org",
    }
  • meok_dora_tlpt_planner/server.py:364-364 (registration)
    The `@mcp.tool()` decorator registers `pricing` as an MCP tool via the FastMCP instance.
    @mcp.tool()

Tool Definition Quality

C2.9/5.0
Behavior2/5

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

No annotations are provided, and the description does not disclose any behavioral traits such as side effects, permissions, or rate limits. The agent has no insight into whether the tool is read-only or requires special access.

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 a single sentence with no redundancy, making it concise. However, it is so brief that it sacrifices necessary detail, which prevents a higher score.

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

Completeness2/5

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

With zero parameters and an output schema present, the description should explain what pricing information is returned (e.g., costs, tiers, or conditions). It fails to do so, leaving the agent without sufficient context to trust the tool's relevance.

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?

The tool has zero parameters, so baseline is 4. However, the description ('Pricing...') does not add value beyond the empty schema—it merely restates the tool name. It could describe the output structure or content, which is absent.

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

Purpose4/5

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

The description clearly states 'Pricing for MEOK DORA TLPT Planner,' indicating this tool provides pricing information. It distinguishes from sibling tools (e.g., list_phases, scope_tlpt) by focusing on pricing. However, it lacks a specific verb (e.g., 'get' or 'retrieve'), which would improve precision.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent to guess its appropriate role.

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-dora-tlpt-planner-mcp'

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