Synthex Forge — x402 Paid Agent Services

Create Sla Breach Evidence

create_sla_breach_evidence

Destructive

Evidence package for a vendor SLA breach. use it rather than create_fund_tearsheet for sla breach evidence, not fund tearsheet; an object with 52 fields including _dt, against. $1 USDC.

Input Schema

Name	Required	Description
`url`	Yes	The URL to fetch, verify or route to.
`claimed_sla`	No	The claimed sla this operation operates on. See the schema for its type and whether it is required.
`window_hours`	No	How far back to look, in hours.

Output Schema

Name	Required	Description
`n`	No	The `n` field of the response.
`ok`	Yes	Whether the operation succeeded.
`ts`	No	The `ts` field of the response.
`_dt`	No	The `_dt` field of the response.
`max`	No	The `max` field of the response.
`min`	No	The `min` field of the response.
`p50`	No	The `p50` field of the response.
`p95`	No	The `p95` field of the response.
`p99`	No	The `p99` field of the response.
`url`	No	The `url` field of the response.
`note`	No	A note on how the answer was produced.
`rows`	No	The `rows` field of the response.
`error`	No	The machine-readable error code, when the operation failed.
`value`	No	The `value` field of the response.
`breach`	No	The `breach` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`metric`	No	The `metric` field of the response.
`p95_ms`	No	The `p95_ms` field of the response.
`pay_to`	No	The `pay_to` field of the response.
`sample`	No	The `sample` field of the response.
`sha256`	No	The `sha256` field of the response.
`target`	No	The `target` field of the response.
`uptime`	No	The `uptime` field of the response.
`window`	No	The `window` field of the response.
`against`	No	The `against` field of the response.
`claimed`	No	The `claimed` field of the response.
`network`	No	The `network` field of the response.
`planned`	No	The `planned` field of the response.
`verdict`	Yes	The decision this tool returned.
`breached`	No	The `breached` field of the response.
`coverage`	No	How much of the underlying corpus the answer is based on.
`evidence`	No	The `evidence` field of the response.
`measured`	No	The `measured` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`price_usd`	No	The price of the operation that was paid.
`shortfall`	No	The `shortfall` field of the response.
`latency_ms`	No	The `latency_ms` field of the response.
`normalised`	No	The `normalised` field of the response.
`package_id`	No	The `package_id` field of the response.
`public_key`	No	The `public_key` field of the response.
`window_end`	No	The `window_end` field of the response.
`http_status`	No	The `http_status` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`p95_delta_ms`	No	The `p95_delta_ms` field of the response.
`probe_method`	No	The `probe_method` field of the response.
`uptime_delta`	No	The `uptime_delta` field of the response.
`window_hours`	No	The `window_hours` field of the response.
`window_start`	No	The `window_start` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`profileVersion`	No	Version of the answer profile.
`required_probes`	No	The `required_probes` field of the response.
`declared_price_usd`	No	The `declared_price_usd` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed54 schema fields changedOct 31, 2026

addedOutput schema / properties / _dt

Added value: +{
+  "description": "The `_dt` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / against

Added value: +{
+  "description": "The `against` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / breach

Added value: +{
+  "description": "The `breach` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / breached

Added value: +{
+  "description": "The `breached` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / claimed

Added value: +{
+  "description": "The `claimed` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / coverage

Added value: +{
+  "description": "How much of the underlying corpus the answer is based on.",
+  "type": "object"
+}

addedOutput schema / properties / coverage_gaps

Added value: +{
+  "description": "The `coverage_gaps` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / declared_price_usd

Added value: +{
+  "description": "The `declared_price_usd` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / detail

Added value: +{
+  "description": "Human-readable explanation of the verdict.",
+  "type": "string"
+}

addedOutput schema / properties / error

Added value: +{
+  "description": "The machine-readable error code, when the operation failed.",
+  "type": "string"
+}

addedOutput schema / properties / evidence

Added value: +{
+  "description": "The `evidence` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / http_status

Added value: +{
+  "description": "The `http_status` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / latency_ms

Added value: +{
+  "description": "The `latency_ms` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / max

Added value: +{
+  "description": "The `max` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / measured

Added value: +{
+  "description": "The `measured` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / metric

Added value: +{
+  "description": "The `metric` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / min

Added value: +{
+  "description": "The `min` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / n

Added value: +{
+  "description": "The `n` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / network

Added value: +{
+  "description": "The `network` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / normalised

Added value: +{
+  "description": "The `normalised` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / ok

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / p50

Added value: +{
+  "description": "The `p50` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / p95

Added value: +{
+  "description": "The `p95` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / p95_delta_ms

Added value: +{
+  "description": "The `p95_delta_ms` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / p95_ms

Added value: +{
+  "description": "The `p95_ms` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / p99

Added value: +{
+  "description": "The `p99` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / package_id

Added value: +{
+  "description": "The `package_id` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / pay_to

Added value: +{
+  "description": "The `pay_to` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / planned

Added value: +{
+  "description": "The `planned` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / price_usd

Added value: +{
+  "description": "The price of the operation that was paid.",
+  "type": "number"
+}

addedOutput schema / properties / probe_method

Added value: +{
+  "description": "The `probe_method` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / profileVersion

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / public_key

Added value: +{
+  "description": "The `public_key` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / required_probes

Added value: +{
+  "description": "The `required_probes` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / rows

Added value: +{
+  "description": "The `rows` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sample

Added value: +{
+  "description": "The `sample` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / shortfall

Added value: +{
+  "description": "The `shortfall` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / signed_over

Added value: +{
+  "description": "The `signed_over` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / target

Added value: +{
+  "description": "The `target` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / ts

Added value: +{
+  "description": "The `ts` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / uptime

Added value: +{
+  "description": "The `uptime` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / uptime_delta

Added value: +{
+  "description": "The `uptime_delta` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / url

Added value: +{
+  "description": "The `url` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / value

Added value: +{
+  "description": "The `value` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / window

Added value: +{
+  "description": "The `window` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / window_end

Added value: +{
+  "description": "The `window_end` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / window_hours

Added value: +{
+  "description": "The `window_hours` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / window_start

Added value: +{
+  "description": "The `window_start` field of the response.",
+  "type": "object"
+}

addedOutput schema / required

Added value: +[
+  "detail",
+  "ok",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare this a destructive, non-idempotent write, and the description adds a genuinely non-annotated trait: it costs $1 USDC. However, for a destructive, non-idempotent mutation it says nothing about what is written or overwritten, whether the package can be regenerated, or what authorization is needed. The 52-field output note is largely redundant given an output schema exists.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and alternative are front-loaded and the whole thing is short. But the second half is garbled — "an object with 52 fields including _dt, against. $1 USDC." is a truncated fragment — and the field-count detail duplicates the output schema rather than earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values needn't be explained, and the description covers purpose, alternative, and cost. What's missing is behavior around a destructive, non-idempotent, paid write: what the evidence package consists of, whether repeated calls create duplicates, and any preconditions for the nested `claimed_sla` input.

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 description coverage is 100%, which sets the baseline at 3, but the schema's own text is templated ("The URL to fetch, verify or route to"; "See the schema for its type and whether it is required"). The description adds nothing about the required URL, the nested `claimed_sla` object, or the 168-hour default on `window_hours`, so it neither compensates nor regresses.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific artifact — an evidence package for a vendor SLA breach — and explicitly contrasts it with `create_fund_tearsheet`, so the resource and scope are unambiguous. It lacks an explicit verb ("creates"), but the tool name and title supply that, leaving only a minor gap.

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?

It gives an explicit routing rule: use this rather than `create_fund_tearsheet` for SLA breach evidence, not fund tearsheets. That is real when-to-use guidance against a named alternative. It stops short of covering prerequisites (permissions, when an SLA breach is substantiated) or differentiating from the other evidence-producing siblings such as `create_audit_evidence_package` or `ingest_evidence`.

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

All Synthex Forge — x402 Paid Agent Services 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.