Skip to main content
Glama

dora_third_party_risk

Read-onlyIdempotent

[Deterministic regulatory contract audit. Pure calculation, read-only, side-effect free]. Audits ICT third-party service provider contracts under DORA Articles 28-30: mandatory exit strategies, regulator inspection rights, EEA data processing location guarantees, subcontractor change notification windows, and 24h incident reporting clauses. Usage: Use this tool to audit ICT vendor agreements for financial institutions. For entity NIS2 classification, use 'nis2_criticality_classifier'. For cyber incident triage, use 'incident_severity_triage'. Returns: JSON object with { isCompliant: boolean, compliantClausesCount: number, missingClauses: string[], riskLevel: 'LOW' | 'MEDIUM' | 'CRITICAL', recommendations: string[] }.

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 (e.g. AWS Europe, Microsoft Azure)
contractClausesYesKey contractual clauses required by DORA Art. 30
serviceCategoryYesCategory of ICT service provided
isCriticalFunctionYesWhether this service supports a critical or important financial function

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, and the description reinforces this with 'pure calculation, side-effect free' plus determinism, which is meaningful for audit output reproducibility. It also discloses the return payload keys (isCompliant, riskLevel, missingClauses, recommendations), adding value beyond the annotations, though it says nothing about the 24h threshold semantics or how a partial/non-compliant input is scored.

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?

Front-loaded with the core purpose, then Usage, then Returns — a clean structure with no filler sentences. The bracketed tag preamble is slightly redundant with the annotations but is short enough not to be harmful.

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?

For a 4-parameter tool with a nested object and no output schema, the description supplies both the audited clause dimensions and an explicit return shape, so an agent can call it and interpret results without further documentation. Nothing essential for correct invocation is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description earns above that by tying the nested clause booleans to concrete DORA Article 30 obligations, including the 24-hour incident notification window that corresponds to hasIncidentNotificationWindowHours. It does not explain how isCriticalFunction or serviceCategory alter the compliance verdict.

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 — auditing ICT third-party provider contracts under DORA Articles 28-30 — and enumerates the exact clause dimensions checked (exit strategies, regulator inspection rights, EEA data location, subcontractor notification, 24h incident reporting). This is unmistakably distinct from the sibling classifiers and triage tools.

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?

It states the use case (financial institutions auditing ICT vendor agreements) and explicitly routes two adjacent needs elsewhere: 'nis2_criticality_classifier' for entity classification and 'incident_severity_triage' for incident triage. The agent does not have to guess which sibling applies.

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