Skip to main content
Glama

NovaPixel LexGrid

dora_third_party_risk

Audits ICT vendor contracts under DORA Articles 28-30: mandatory exit strategies, regulator inspection rights, EEA data processing location and incident notification windows.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "providerName": "<providerName>",
      "serviceCategory": "<serviceCategory>",
      "isCriticalFunction": "<isCriticalFunction>",
      "contractClauses": "<contractClauses>"
    },
    "name": "dora_third_party_risk"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerNameYesICT third-party service provider name
contractClausesYes
serviceCategoryYes
isCriticalFunctionYesWhether this service supports a critical or important financial function

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It names audit dimensions but does not disclose whether the operation is read-only, what it returns, how findings are scored, permission requirements, or side effects.

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 dense but front-loaded sentence. Every clause names a concrete audit dimension, and there is no filler or repetition.

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 4-parameter nested audit tool with no annotations and no output schema, the description omits return format, pass/fail logic, and several parameter semantics. The audit scope is clear, but the definition is not complete enough for reliable invocation.

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 50%. The description maps several contractClauses fields to DORA concepts (exit strategy, regulator inspection rights, EEA data location, incident notification windows), but it does not explain providerName, serviceCategory, or isCriticalFunction beyond what the schema already provides.

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?

States a specific verb ('Audits') and resource ('ICT vendor contracts under DORA Articles 28-30'), plus concrete audit dimensions. It does not explicitly differentiate this tool from the sibling compliance tools, so it is clear but not fully sibling-aware.

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?

Implies usage for DORA vendor-contract audits, but gives no explicit when-to-use, when-not-to-use, prerequisites, or alternatives to sibling tools such as incident_severity_triage or nis2_criticality_classifier.

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