Ground Truth - Fresh Evidence for AI Agents

Compliance Signal Scan

assess_compliance_posture

Read-onlyIdempotent

Scan a public security, trust, compliance, or legal page for common enterprise buying signals before you claim a vendor supports a particular compliance posture. It looks for public references to SOC 2, ISO 27001, GDPR, HIPAA, DPA terms, subprocessors, SSO, SCIM, encryption, and data residency language. This is a signal scanner, not proof of certification or legal sufficiency.

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": {
      "url": "<url>"
    },
    "name": "assess_compliance_posture"
  }
}

Input Schema

Name	Required	Description	Default
`url`	Yes	Public trust, security, compliance, or policy URL to scan.

Output Schema

Name	Required	Description
`url`	Yes	Compliance or trust page that was analyzed.
`error`	No	Fetch or parsing error when the page could not be analyzed.
`cached`	No	True when the page body came from the 5-minute cache.
`signals`	No	Boolean scan results for common enterprise compliance and security signals.
`pageLength`	No	Size of the fetched page body in characters.
`matchedSignals`	No	Signal names that were detected on the page.

Schema Changelog

Changes observed during successful MCP inspections.

Changed10 schema fields changedMay 6, 2026

addedOutput schema / properties / signals / properties / dataResidency / description

Added value: +"True when the page references data residency, data regions, or regional storage controls."

addedOutput schema / properties / signals / properties / dpa / description

Added value: +"True when the page references a data processing agreement or DPA."

addedOutput schema / properties / signals / properties / encryption / description

Added value: +"True when the page references encryption, data encrypted at rest, or data encrypted in transit."

addedOutput schema / properties / signals / properties / gdpr / description

Added value: +"True when the page references GDPR or the General Data Protection Regulation."

addedOutput schema / properties / signals / properties / hipaa / description
```
Added value: +"True when the page references HIPAA compliance language."
```

addedOutput schema / properties / signals / properties / iso27001 / description

Added value: +"True when the page references ISO 27001 certification or compliance language."

addedOutput schema / properties / signals / properties / scim / description
```
Added value: +"True when the page references SCIM provisioning."
```

addedOutput schema / properties / signals / properties / soc2 / description

Added value: +"True when the page references SOC 2 or SOC2 compliance language."

addedOutput schema / properties / signals / properties / sso / description
```
Added value: +"True when the page references SSO or single sign-on."
```
addedOutput schema / properties / signals / properties / subprocessorList / description
```
Added value: +"True when the page references subprocessors or a subprocessor list."
```

First observedApr 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context about the tool's limitations ('not proof of certification or legal sufficiency') and the types of signals it scans for, going beyond the structured fields.

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 three concise sentences: the first states the action and purpose, the second lists specific signal types, and the third caveats limitations. Every sentence adds value with no waste, and the key information is front-loaded.

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 simple one-parameter tool with a complete schema and output schema, the description provides thorough context: what it scans, what it looks for, and its limitations. No critical information is missing for an agent to select and invoke the tool correctly.

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?

The schema covers 100% of parameter descriptions, so the description doesn't need to elaborate on the 'url' parameter. The description mentions 'public' pages, which aligns with the schema description and adds minimal extra meaning, making a baseline 3 appropriate.

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 clearly states the tool scans public security, trust, compliance, or legal pages for common enterprise buying signals, using a specific verb and resource. It distinguishes itself by specifying the compliance-posture-related use case and listing concrete signal types, standing out from sibling tools.

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?

The description gives clear context on when to use the tool ('before you claim a vendor supports a particular compliance posture') and notes it is a signal scanner, not proof. It does not explicitly name alternatives or exclusions, but the context is sufficient for an agent to infer appropriate usage.

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

All Ground Truth - Fresh Evidence for AI Agents 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.