Skip to main content
Glama
CSOAI-ORG

MEOK DORA Tlpt Planner MCP

signed_tlpt_attestation

Generate an HMAC-signed TLPT attestation with verification URL for financial entities, requiring entity name, scope summary, test phase, and findings summary.

Instructions

Produce an HMAC-signed TLPT attestation via the public meok-attestation-api.

Args: entity_name: Legal name of the financial entity. scope_summary: 1-3 sentence summary of test scope. test_phase: One of preparation / testing / closure. findings_summary: Dict with findings_count, severity_distribution, and summary text. signing_role: Role of the signer (default white-team-lead).

Returns: Signed attestation with verification URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
entity_nameYes
scope_summaryYes
test_phaseYes
findings_summaryYes
signing_roleNowhite-team-lead

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The @mcp.tool() decorated function 'signed_tlpt_attestation' that implements the tool logic. It builds a DORA TLPT attestation payload, sends it to the meok-attestation-api /sign endpoint, and returns the signed attestation with a verification URL. On API failure, it returns a fallback self-attestation payload.
    @mcp.tool()
    def signed_tlpt_attestation(
        entity_name: str,
        scope_summary: str,
        test_phase: str,
        findings_summary: dict[str, Any],
        signing_role: str = "white-team-lead",
    ) -> dict[str, Any]:
        """Produce an HMAC-signed TLPT attestation via the public meok-attestation-api.
    
        Args:
            entity_name: Legal name of the financial entity.
            scope_summary: 1-3 sentence summary of test scope.
            test_phase: One of preparation / testing / closure.
            findings_summary: Dict with findings_count, severity_distribution, and summary text.
            signing_role: Role of the signer (default white-team-lead).
    
        Returns:
            Signed attestation with verification URL.
        """
        payload = {
            "kind": "dora-tlpt-attestation",
            "entity": entity_name,
            "scope": scope_summary,
            "phase": test_phase,
            "findings": findings_summary,
            "signing_role": signing_role,
            "signed_at": datetime.now(timezone.utc).isoformat(),
            "regulatory_basis": "DORA Reg (EU) 2022/2554 Art. 26-27 + TIBER-EU v2.0",
            "tool": "meok-dora-tlpt-planner-mcp",
            "tool_version": "1.0.0",
        }
    
        try:
            req = urllib.request.Request(
                f"{ATTESTATION_API}/sign",
                data=json.dumps({"payload": payload, "type": "dora-tlpt"}).encode("utf-8"),
                headers={"Content-Type": "application/json"},
            )
            with urllib.request.urlopen(req, timeout=10) as resp:
                result = json.loads(resp.read().decode("utf-8"))
            return {
                "ok": True,
                "payload": payload,
                "signature": result.get("signature"),
                "verify_url": result.get("verify_url"),
                "attestation_id": result.get("attestation_id"),
            }
        except urllib.error.URLError as e:
            return {
                "ok": False,
                "error": f"attestation API unreachable: {e}",
                "payload": payload,
                "fallback": "Use the payload above as a self-attestation; sign locally with your own HMAC key.",
            }
  • The @mcp.tool() decorator registers 'signed_tlpt_attestation' as an MCP tool with the FastMCP server instance.
    @mcp.tool()
  • The ATTESTATION_API constant used by the handler to send the signing request to the meok-attestation-api.
    ATTESTATION_API = os.environ.get("MEOK_ATTESTATION_API", "https://meok-attestation-api.vercel.app")
Behavior2/5

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

No annotations are provided, so the description carries full burden. It indicates the action produces a signed attestation but does not disclose side effects, authorization requirements, or whether the action is idempotent. This is insufficient for safe invocation.

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 concise: a one-line purpose followed by a bullet-like list of arguments. It front-loads the purpose and uses no filler, but could be more structured (e.g., markdown formatting).

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?

The description covers all input parameters and mentions the return value. However, it lacks constraints (e.g., signing_role values beyond the default) and does not explain the output schema in detail. The output schema exists but is not leveraged.

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?

With 0% schema description coverage, the description adds significant meaning: it explains the expected structure of findings_summary (dict with specific keys), lists enum values for test_phase, and notes the default for signing_role. This goes beyond the raw 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 clearly states the tool produces an HMAC-signed TLPT attestation via a specific API, and lists all arguments. It is distinct from sibling tools like list_phases or pricing, which have different purposes.

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?

The description implies usage when a signed attestation is needed, but does not explicitly state when to use this tool versus alternatives or provide any exclusion criteria.

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