Nopaque TotalPath

Get Voice Compliance Report

getComplianceReportByPhone

Read-onlyIdempotent

Get the voice compliance report for one phone number: takes phoneNumber (required, E.164, e.g. +442012345678, from listComplianceReports) and optional sector. Built from the latest run of each compliance catalogue test against that number, with a summary (ran, passed, failed of the tests that apply) and the tests grouped by regulation, each with its verdict, the judge's reasoning and evidence, and the run it came from (runId). Use when: the user asks whether a number is compliant or which compliance checks it fails. For a single run's detail use getRunResults with the run id. Read-only. Needs testing:read. Only your workspace's runs are read.

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": {
      "phoneNumber": "<phoneNumber>"
    },
    "name": "getComplianceReportByPhone"
  }
}

Input Schema

Name	Required	Description	Default
`sector`	No	Sector filter (e.g. `financial-services`). Omit to include all sectors.
`phoneNumber`	Yes	URL-encoded E.164 phone number (e.g. `%2B442012345678` for `+442012345678`). The handler `decodeURIComponent`s before reading; raw `+` works on most clients too, but encoding is recommended.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations, the description adds important context: it is read-only, requires the `testing:read` permission, and only reads runs from the caller's workspace. It also explains that the report is built from the latest run of each applicable compliance catalogue test.

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?

The description is front-loaded with the core action and then adds use guidance, output structure, permissions, and the relevant alternative. Every sentence contributes useful information without repetition or filler.

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?

Given the annotations and output schema, the description is complete: it covers the data source, report contents, use case, access permission, workspace scope, and when to use a sibling tool instead. 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both parameters are already fully documented in the input schema. The description notes that `phoneNumber` is required and comes from `listComplianceReports`, but adds little semantic detail beyond the schema, which already covers E.164 formatting, URL encoding, and sector filtering.

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 states a specific verb and resource: 'Get the voice compliance report for one phone number'. It also explicitly distinguishes the tool from getRunResults and points to listComplianceReports as the source of the phone number.

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 gives an explicit use case: 'Use when: the user asks whether a number is compliant or which compliance checks it fails.' It also names the alternative for single-run details and explains where to obtain the required phone number.

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.