Nopaque TotalPath

List Compliance Catalogue

listComplianceCatalogue

Read-onlyIdempotent

List the available compliance tests in the regulatory catalogue (e.g., GDPR consent capture, EU AI Act disclosure, PCI-DSS DTMF masking). Each entry has an ID + sector + description. Use the IDs as input to runComplianceTest.

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": "listComplianceCatalogue"
  }
}

Input Schema

Name	Required	Description	Default
`sector`	No	Sector filter (e.g. `financial-services`). Omit to receive all sectors.

Output Schema

Name	Required	Description
`tier`	Yes
`catalogue`	Yes	Bundled compliance catalogue. Filtered server-side to the workspace's sector (`all` always included; other sectors only when the query string `sector` matches). Deprecated tests are stripped.
`pickerLimit`	Yes	Maximum number of tests the workspace's tier may dispatch in one batch.
`s2stestSecondsAvailable`	Yes	Remaining s2stest seconds in the workspace's quota.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds useful context beyond that: the catalogue is regulatory in scope and each record carries ID, sector and description. No pagination or catalogue-staleness note, which keeps it short of a 5.

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?

Three short sentences, each doing a distinct job: define the resource, describe the entry shape, and hand off to the consuming tool. Front-loaded and free of filler.

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?

An output schema exists, so return values need not be explained, and the description still sketches the entry fields. For a single-parameter read tool this is essentially complete; only the relationship to other compliance-list siblings is left implicit.

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%: the single sector parameter is already documented with an example and the 'omit to receive all sectors' behaviour. The description adds no parameter detail beyond that, so the baseline 3 applies.

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?

States a specific verb and resource ('List the available compliance tests in the regulatory catalogue') and immediately disambiguates it from sibling list tools by naming concrete examples (GDPR consent capture, EU AI Act disclosure, PCI-DSS DTMF masking). It also says what an entry contains, so the agent knows the shape of the result before calling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent forward: 'Use the IDs as input to runComplianceTest' — a clear this-then-that workflow. It does not contrast with the other catalogue-adjacent siblings (listComplianceReports, listDigitalComplianceAudits), so the selection guidance is clear but incomplete.

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

All Nopaque TotalPath tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.