Synthex Forge — x402 Paid Agent Services

Issue Uptime Attestation

issue_uptime_attestation

Destructive

The uptime of a vendor's API, measured by us and signed. use it rather than issue_attestation for uptime attestation, not attestation; an object with 39 fields including _dt, algorithm. $0.1 USDC.

Input Schema

Name	Required	Description	Default
`url`	Yes	The URL to fetch, verify or route to.
`window_hours`	No	How far back to look, in hours.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the operation succeeded.
`to`	No	The `to` field of the response.
`ts`	No	The `ts` field of the response.
`_dt`	No	The `_dt` field of the response.
`from`	No	The `from` field of the response.
`gaps`	No	The `gaps` 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.
`total`	No	The `total` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`failed`	No	The `failed` field of the response.
`pay_to`	No	The `pay_to` field of the response.
`probes`	No	The `probes` field of the response.
`reason`	No	Why the verdict was reached.
`sha256`	No	The `sha256` field of the response.
`target`	No	The `target` field of the response.
`uptime`	No	The `uptime` 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.
`coverage`	No	How much of the underlying corpus the answer is based on.
`algorithm`	No	The `algorithm` field of the response.
`price_usd`	No	The price of the operation that was paid.
`latency_ms`	No	The `latency_ms` field of the response.
`normalised`	No	The `normalised` 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.
`measured_by`	No	The `measured_by` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`probe_method`	No	The `probe_method` 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.
`declared_price_usd`	No	The `declared_price_usd` field of the response.
`planned_gaps_excluded`	No	The `planned_gaps_excluded` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed41 schema fields changedOct 31, 2026

addedOutput schema / properties / _dt

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

addedOutput schema / properties / algorithm

Added value: +{
+  "description": "The `algorithm` 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 / failed

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

addedOutput schema / properties / from

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

addedOutput schema / properties / gaps

Added value: +{
+  "description": "The `gaps` 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 / measured_by

Added value: +{
+  "description": "The `measured_by` 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 / 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 / planned_gaps_excluded

Added value: +{
+  "description": "The `planned_gaps_excluded` 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 / probes

Added value: +{
+  "description": "The `probes` 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 / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / rows

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

addedOutput schema / properties / sha256

Added value: +{
+  "description": "The `sha256` 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 / to

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

addedOutput schema / properties / total

Added value: +{
+  "description": "The `total` 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 / 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_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

B3.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description does not contradict that but also does not explain why a signed attestation issuance is flagged destructive or non-idempotent. It does add genuinely useful info annotations lack: the paid nature and price ($0.1 USDC) and the 39-field response including _dt and algorithm.

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

Conciseness2/5

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

It is short, but the structure is telegraphic and garbled: 'not attestation', dropped articles, and a bare '$0.1 USDC.' fragment. The single most useful fact for an agent (payment required) trails at the very end, and the sibling-routing clause is written in a way that must be re-read to parse.

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?

An output schema exists, so the terse field summary is a bonus rather than a requirement. However, for a paid, non-idempotent write tool the description never covers what the signature attests to, what happens on payment or fetch failure, or how `url` relates to the measured endpoint.

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% (url and window_hours are both documented in-schema), so the baseline is 3. The description adds nothing about what `url` should point to or how `window_hours` affects the measurement window, so it does not exceed the schema.

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

Purpose3/5

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

The description names the specific resource (a vendor API's uptime, measured internally and signed) but states it as a noun phrase rather than a verb+resource action, so the issuing action only comes from the tool name. The differentiating clause 'use it rather than `issue_attestation` for uptime attestation, not attestation' is grammatically self-cancelling and leaves ambiguity about what is actually produced.

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 explicitly routes the agent away from a sibling: use this rather than `issue_attestation` for uptime attestation. That is a real when/when-not condition, though it is mangled and omits the closest sibling, `verify_mcp_uptime` (verify vs. issue), which an agent could easily confuse this with.

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.