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

Start Pipeline Session

dcl_pipeline_start

SESSION Management ($0.05). Generates a new pipeline_id and returns session metadata (scope, expiry, initial drift_mode) for organizing a series of related checks under one identifier. Note: this call does not currently link the returned pipeline_id to later evaluate_* calls — there is no server-side session state that ties subsequent audits back to it; it is an identifier/timestamp issuer, not an active tracking session. Use this to obtain a shared reference ID for your own client-side grouping of a multi-step audit sequence; do not rely on it to automatically aggregate drift across calls.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`scope`	No	Scope label for the session.	default
`agent_id`	Yes	Identifier of the agent that owns this session.
`ttl_seconds`	No	Session time-to-live, in seconds.

Output Schema

TableJSON Schema

Name	Required	Description
`scope`	Yes	Scope label for the session.
`agent_id`	Yes	Identifier of the agent that owns this session.
`drift_mode`	Yes	Drift status at session start (always NORMAL for a new session).
`expires_at`	Yes	Unix timestamp when the session expires.
`pipeline_id`	Yes	Unique identifier for the newly opened pipeline session.

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.6/5.0

Behavior5/5

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

The description adds crucial behavioral context beyond the annotations by disclosing that there is no server-side session state and that the pipeline_id is not connected to subsequent evaluate_* calls. It also mentions the cost and the returned metadata fields, giving the agent an accurate model of what the tool does and does not do.

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?

The description is front-loaded with the core action and uses a follow-up sentence for important caveats and usage guidance. It is a bit long and somewhat repetitive around the 'no session state' idea, but every sentence contributes value.

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 three-parameter tool with an output schema available, the description covers the generated ID, returned metadata, intended use, monetary cost, limitations, and non-linkage to later audit calls. Nothing required for correct invocation and expectation-setting 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?

The input schema fully documents all three parameters with descriptions and defaults, so the description does not need to explain them. The description adds little parameter-level detail beyond mentioning scope and expiry in the return metadata, placing it at the schema-covered baseline of 3.

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 a specific action and resource: 'Generates a new pipeline_id and returns session metadata.' It also differentiates this tool from the many evaluate_* siblings by explicitly positioning it as an identifier/timestamp issuer rather than an active tracking session.

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 provides explicit usage instructions: 'Use this to obtain a shared reference ID for your own client-side grouping of a multi-step audit sequence.' It also gives a clear exclusion: 'do not rely on it to automatically aggregate drift across calls,' and warns that later evaluate_* calls are not linked to this ID.

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.