DCL Trust Oracle — AI/LLM Output Audit (x402 MCP)

Fast Pre-Action Audit

dcl_evaluate_fast

FAST Pre-Action Audit ($0.01). Runs the response through the server's "default" policy: a substring check against 3 forbidden phrases ("ignore previous instructions", "jailbreak", "bypass safety") with a 0.7 minimum-confidence threshold. Each forbidden match found costs 0.4 confidence; if confidence falls below 0.7, or any match is found, the verdict is NO_COMMIT and reason lists which phrase triggered it. Otherwise COMMIT. Use this as the default low-cost first-pass gate before a risky agent action; switch to dcl_evaluate_strict for a broader, higher-bar check, or to dcl_evaluate_jailbreak / dcl_evaluate_safety / dcl_evaluate_quality for a narrower, single-topic check instead of the general-purpose default policy.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`agent_id`	Yes	Identifier of the agent that produced the response.
`response`	Yes	The agent or LLM response text to audit.

Output Schema

TableJSON Schema

Name	Required	Description
`reason`	Yes	Human-readable explanation of why the verdict was reached.
`tx_hash`	Yes	Hash of this record in the tamper-evident audit chain.
`verdict`	Yes	COMMIT if the response passed policy checks, otherwise NO_COMMIT.
`seal_text`	Yes	Human-readable Leibniz Layer verification seal.
`timestamp`	Yes	Unix timestamp when this record was sealed.
`confidence`	Yes	Confidence score of the verdict, from 0.0 to 1.0.
`drift_mode`	Yes	Current drift status: NORMAL, WARNING, ESCALATION, or BLOCK.
`input_hash`	Yes	Hash of the evaluated response (raw content is never stored).
`verify_url`	Yes	Public URL to independently verify this seal.
`chain_index`	Yes	Sequential index of this record in the audit chain.
`drift_score`	Yes	Z-score measuring deviation of the recent commit rate from baseline.
`policy_version`	Yes	Version of the policy that was applied.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedAug 6, 2026

removedInput schema / properties / payment_id

Removed value: -{
-  "default": "",
-  "description": "Optional payment identifier returned by a previous call when payment is required",
-  "title": "Payment Id",
-  "type": "string"
-}

First observedAug 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

With annotations providing no positive safety hints (all false), the description carries the full burden and fully delivers: it discloses the $0.01 cost, the exact forbidden phrases, the 0.4 confidence penalty per match, the 0.7 threshold, and the precise verdict/reason behavior. This is far more behavioral detail than annotations alone provide.

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 front-loads the purpose and cost, then gives the decision algorithm, and ends with routing guidance. Every sentence carries essential operational information and none is filler, so the length is justified by the complexity.

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 two-parameter tool with an output schema, the description covers the policy details, cost, verdict semantics, and when to prefer sibling tools. There is no obvious gap that would prevent an agent from selecting and invoking this 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 input schema already documents both parameters (response and agent_id) at 100% coverage, so the description does not need to add parameter-level semantics. The description adds no new meaning beyond the schema for these two parameters, hence the baseline score.

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 opens with a precise verb and resource: it runs the response through the server's default policy, and specifies the output verdicts (COMMIT vs NO_COMMIT) and triggering conditions. It also differentiates itself from named siblings (dcl_evaluate_strict, dcl_evaluate_jailbreak, etc.), so an agent can reliably pick it among the many dcl_evaluate_* 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 explicitly instructs to use this as the default low-cost first-pass gate before risky agent actions, and tells exactly when to switch to dcl_evaluate_strict or to the narrower single-topic evaluators. No other tool in the set is given such direct selection guidance.

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

All DCL Trust Oracle — AI/LLM Output Audit (x402 MCP) 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.