Skip to main content
Glama
CSOAI-ORG

MEOK DORA Tlpt Planner MCP

list_phases

Retrieve the three TIBER-EU TLPT phases and their deliverables to plan your compliance process.

Instructions

List the 3 TIBER-EU TLPT phases with deliverables.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler function decorated with @mcp.tool() that returns the TIBER_PHASES constant dictionary containing the 3 TIBER-EU TLPT phases (preparation, testing, closure) with their durations, descriptions, deliverables, and stakeholders.
    @mcp.tool()
    def list_phases() -> dict[str, Any]:
        """List the 3 TIBER-EU TLPT phases with deliverables."""
        return TIBER_PHASES
  • The TIBER_PHASES constant dictionary that serves as the data/return schema for the list_phases tool. Contains the three phases: preparation (4-8 weeks), testing (12-16 weeks), and closure (6-10 weeks), each with duration, description, deliverables list, and stakeholders list.
    TIBER_PHASES = {
        "preparation": {
            "duration_weeks": "4-8",
            "description": "Scope definition, white-team assembly, threat-intel commission",
            "deliverables": [
                "TLPT scope document (critical/important functions selected)",
                "White-team Terms of Reference (ToR)",
                "Threat-intelligence provider engagement letter",
                "Red-team provider qualification (DORA Art. 27 RTS)",
                "Notification to lead overseer (TIBER-EU Cyber Team / national authority)",
            ],
            "stakeholders": ["white-team-lead", "ciso", "head-of-it-risk", "tlpt-cyber-team"],
        },
        "testing": {
            "duration_weeks": "12-16",
            "description": "Threat intelligence + red-team engagement against live production",
            "deliverables": [
                "Targeted Threat Intelligence (TTI) report",
                "Red-team Test Plan (TTP-mapped to MITRE ATT&CK)",
                "Live red-team engagement against production systems",
                "Daily situation reports to white-team",
                "Test summary findings report",
            ],
            "stakeholders": ["red-team", "threat-intel-provider", "white-team-lead"],
        },
        "closure": {
            "duration_weeks": "6-10",
            "description": "Findings, remediation, replay, attestation",
            "deliverables": [
                "Findings report with severity-ranked detected gaps",
                "Remediation plan (90/180/365-day milestones)",
                "Purple-team replay test (validate fixes)",
                "Final TLPT attestation (signed by white-team + RT lead)",
                "Submission to lead overseer for sign-off (Art. 26(7) DORA)",
            ],
            "stakeholders": ["white-team-lead", "remediation-owner", "lead-overseer"],
        },
    }
  • The tool is registered with FastMCP via the @mcp.tool() decorator on line 358, which registers 'list_phases' as an MCP tool. The FastMCP instance is created on line 22: 'mcp = FastMCP("meok-dora-tlpt-planner")'.
    @mcp.tool()
    def list_phases() -> dict[str, Any]:
        """List the 3 TIBER-EU TLPT phases with deliverables."""
        return TIBER_PHASES
  • The TIBER_PHASES constant is also used as a helper data structure reused by the scope_tlpt tool (line 185) which embeds the phases into its scope document output.
    TIBER_PHASES = {
        "preparation": {
            "duration_weeks": "4-8",
            "description": "Scope definition, white-team assembly, threat-intel commission",
            "deliverables": [
                "TLPT scope document (critical/important functions selected)",
                "White-team Terms of Reference (ToR)",
                "Threat-intelligence provider engagement letter",
                "Red-team provider qualification (DORA Art. 27 RTS)",
                "Notification to lead overseer (TIBER-EU Cyber Team / national authority)",
            ],
            "stakeholders": ["white-team-lead", "ciso", "head-of-it-risk", "tlpt-cyber-team"],
        },
        "testing": {
            "duration_weeks": "12-16",
            "description": "Threat intelligence + red-team engagement against live production",
            "deliverables": [
                "Targeted Threat Intelligence (TTI) report",
                "Red-team Test Plan (TTP-mapped to MITRE ATT&CK)",
                "Live red-team engagement against production systems",
                "Daily situation reports to white-team",
                "Test summary findings report",
            ],
            "stakeholders": ["red-team", "threat-intel-provider", "white-team-lead"],
        },
        "closure": {
            "duration_weeks": "6-10",
            "description": "Findings, remediation, replay, attestation",
            "deliverables": [
                "Findings report with severity-ranked detected gaps",
                "Remediation plan (90/180/365-day milestones)",
                "Purple-team replay test (validate fixes)",
                "Final TLPT attestation (signed by white-team + RT lead)",
                "Submission to lead overseer for sign-off (Art. 26(7) DORA)",
            ],
            "stakeholders": ["white-team-lead", "remediation-owner", "lead-overseer"],
        },
    }
Behavior4/5

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

With no annotations, the description carries the full burden. It correctly indicates a read-only listing operation with no side effects. No further behavioral details (e.g., auth) are needed given the tool's simplicity.

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?

One sentence of 8 words, front-loaded with action ('List'), no wasted words. Perfect conciseness and clarity.

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?

Complete for a simple list tool with 0 parameters and an output schema. The description covers what is listed (3 phases, deliverables) and no additional context is necessary.

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?

No parameters exist, so baseline is 4. The description does not add parameter-specific information, but none is required.

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 lists 'the 3 TIBER-EU TLPT phases with deliverables,' using a specific verb and resource. It distinguishes from siblings like pricing or scope_tlpt, which cover different TIBER-EU aspects.

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

Usage Guidelines3/5

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

No explicit guidance on when to use or avoid this tool vs alternatives. However, the set of siblings are distinct, so usage is implied for listing phases, but lack of explicit context lowers the score.

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