Skip to main content
Glama

NovaPixel LexGrid

tlpt_threat_led_pentest_scope

Assesses Threat-Led Penetration Testing (TLPT) obligation and scope under DORA Articles 26-27 and Joint RTS JC 2024 15 (TIBER-EU framework).

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 used
financialSectorNoDORA financial sector classification
lastTlptTestDateNoLast TLPT test completion date (YYYY-MM-DD)
testerUtilizzatiNoAlias for testerType
settoreFinanziarioNoAlias for financialSector
ultimoTestTlptDataNoAlias for lastTlptTestDate
isSystemicallyImportantNoWhether designated as G-SII or O-SII by ECB/EBA
outsourcedCriticalFunctionsNoList of outsourced critical financial functions
funzioniCriticheEsternalizzateNoAlias for outsourcedCriticalFunctions
volumeTransazioniAnnueMilioniEurNoAlias for annualTransactionVolumeMillionEur
annualTransactionVolumeMillionEurNoAnnual transaction volume in million EUR
totalBalanceSheetAssetsMillionEurNoBalance sheet total assets in million EUR
totaleAttivoStatoPatrimonialeMilioniEurNoAlias for totalBalanceSheetAssetsMillionEur

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure and does not meet it. It never says whether this is a pure read/assessment operation or something that persists state, what form the determination takes, whether it depends on external designations (e.g., ECB/EBA G-SII lists), or what happens when optional inputs are omitted.

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?

A single sentence with zero filler, front-loading the verb and resource before the regulatory citations. Nothing is repeated from the schema and no sentence is wasted.

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?

For a tool with 13 parameters, no required fields, no annotations, and no output schema, the description is far too thin. It does not explain what the assessment returns (a boolean obligation? a scope description? a rationale?), nor how the sector/volume/asset parameters feed the determination, leaving the agent unable to predict the result or judge input sufficiency.

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 description coverage is 100%, so every one of the 13 parameters (including the Italian alias pairs) is already documented in the schema itself. The description adds no meaning beyond that — no explanation of how testerType or isSystemicallyImportant influence the obligation outcome — so the baseline 3 applies.

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 states a specific verb ('Assesses') and a specific resource ('TLPT obligation and scope'), and grounds it in named regulations (DORA Articles 26-27, Joint RTS JC 2024 15, TIBER-EU). An agent can tell this is a regulatory applicability/scope determination, distinct in domain from the sibling tools (third-party risk, incident triage, NIS2 criticality), though the description never explicitly names or contrasts those alternatives.

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?

There is no explicit when-to-use, when-not-to-use, or prerequisite guidance. The phrase 'obligation and scope' only weakly implies the use case of determining whether an entity must run a TLPT, and nothing tells the agent what inputs are mandatory or when to prefer a sibling tool instead.

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