Skip to main content
Glama

tlpt_threat_led_pentest_scope

Read-onlyIdempotent

[Deterministic regulatory assessment. Pure calculation, read-only, side-effect free, no external state modified]. Assesses Threat-Led Penetration Testing (TLPT) mandatory obligations and scoping under DORA Articles 26-27 and Joint RTS JC 2024 15 (TIBER-EU framework). Evaluates financial sector type, balance sheet assets (≥30B€ threshold), systemically important institution (G-SII/O-SII) designation, 3-year recurring testing cadence, and required independent external tester qualifications. Usage: Use this tool specifically to determine whether a financial entity is legally mandated to conduct live red-team / TLPT penetration testing under DORA. Do NOT use for general ICT incident classification (use 'incident_severity_triage' instead) or for vendor contract audits (use 'dora_third_party_risk' instead). Returns: JSON object with { isObliged: boolean, rationale: string, recommendedFrequency: string, requiredTesterType: 'EXTERNAL_ACCREDITED' | 'INTERNAL_PERMITTED', legalBasis: string, nextTestDueBy: string | null }.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tlpt_threat_led_pentest_scope"
  }
}

Input Schema

NameRequiredDescriptionDefault
testerTypeNoType of penetration testers utilized (TIBER-EU accreditation)
financialSectorNoDORA financial sector classification under Article 2(1)
lastTlptTestDateNoLast TLPT test completion date in YYYY-MM-DD format
testerUtilizzatiNoItalian alias for testerType
settoreFinanziarioNoItalian alias for financialSector
ultimoTestTlptDataNoItalian alias for lastTlptTestDate
isSystemicallyImportantNoWhether officially designated as G-SII or O-SII by ECB/EBA
outsourcedCriticalFunctionsNoList of outsourced critical financial functions supporting core services
funzioniCriticheEsternalizzateNoItalian alias for outsourcedCriticalFunctions
volumeTransazioniAnnueMilioniEurNoItalian alias for annualTransactionVolumeMillionEur
annualTransactionVolumeMillionEurNoAnnual transaction volume in million EUR
totalBalanceSheetAssetsMillionEurNoTotal balance sheet assets in million EUR (statutory threshold is 30,000 M€)
totaleAttivoStatoPatrimonialeMilioniEurNoItalian alias for totalBalanceSheetAssetsMillionEur

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered; the description adds the substantive behavioral facts that matter here: pure deterministic calculation, no external state modified, and the exact output shape including legalBasis and nextTestDueBy. It stops short of stating precedence rules between the duplicated Italian alias parameters, which is a residual gap for a 13-parameter tool.

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 structure is well front-loaded: bracketed behavioral context, then scope, then usage and exclusions, then returns. It is dense but every block serves a distinct function, though the bracketed 'read-only, side-effect free' clause partly restates the annotations and the Returns block is verbose.

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

Completeness4/5

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

For a 13-parameter, zero-required regulatory assessment tool with no output schema, the description supplies the legal basis, the calculation thresholds, the usage boundary, and a full return-value contract, which is close to sufficient. The one omission is any note on how the Italian alias parameters interact with their English counterparts.

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 coverage is 100%, so every parameter including the Italian aliases is already documented, and the 30,000 M€ threshold is present in the schema itself rather than only in the description. The description adds limited meaning beyond that, mainly tying testerType to the independent external tester qualification requirement. Baseline 3 is appropriate when the schema carries the parameter burden.

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 names a specific verb and resource: assess TLPT mandatory obligations and scoping under DORA Articles 26-27 and RTS JC 2024 15 (TIBER-EU). It also enumerates the factors evaluated (sector, 30B€ asset threshold, G-SII/O-SII status, 3-year cadence, tester qualifications), which clearly distinguishes it from the sibling tools named.

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?

The definition gives an explicit when-to-use condition and two explicit exclusions, each paired with the correct alternative ('incident_severity_triage' for ICT incident classification, 'dora_third_party_risk' for vendor contract audits). No inference is needed to route between tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources