Synthex Forge — x402 Paid Agent Services

Assess Counterparty Risk

assess_counterparty_risk

Read-onlyIdempotent

Price the risk of paying an unknown agent, endpoint or host from YOUR OWN. use it rather than assess_agent_verdict for counterparty risk, not agent verdict; an object with 29 fields including asOf, as_of. $0.5 USDC.

Input Schema

Name	Required	Description
`as_of`	No	The date the answer is computed as of (YYYY-MM-DD). Defaults to today. Use it to reproduce a past answer exactly.
`identifier`	No	The identifier this operation operates on. See the schema for its type and whether it is required.
`observations`	No	The observations this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`asOf`	No	The `asOf` field of the response.
`band`	No	The `band` field of the response.
`kind`	No	The `kind` field of the response.
`name`	No	The `name` field of the response.
`note`	No	A note on how the answer was produced.
`as_of`	No	The date the answer is computed as of.
`score`	No	The numeric score this tool returned.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`weight`	No	The `weight` field of the response.
`factors`	No	The `factors` field of the response.
`signedAt`	No	The `signedAt` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_at`	No	The `signed_at` field of the response.
`signed_by`	No	The key id that signed the answer.
`confidence`	No	Confidence in the verdict, 0 to 1.
`identifier`	No	The `identifier` field of the response.
`public_key`	No	The `public_key` field of the response.
`contribution`	No	The `contribution` field of the response.
`coverageGaps`	No	The `coverageGaps` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`evidence_core`	Yes	The canonical, signed core of the answer — the payload the signature covers.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`missing_fields`	No	The `missing_fields` field of the response.
`profileVersion`	No	Version of the answer profile.
`profile_version`	No	Version of the answer profile.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`signature_algorithm`	No	The `signature_algorithm` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedOct 31, 2026

addedOutput schema / properties / asOf

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

addedOutput schema / properties / as_of

Added value: +{
+  "description": "The date the answer is computed as of.",
+  "type": "string"
+}

addedOutput schema / properties / band

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

addedOutput schema / properties / canonicalization

Added value: +{
+  "description": "The canonicalisation rule the digest was computed under.",
+  "type": "string"
+}

addedOutput schema / properties / confidence

Added value: +{
+  "description": "Confidence in the verdict, 0 to 1.",
+  "type": "number"
+}

addedOutput schema / properties / contribution

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

addedOutput schema / properties / coverageGaps

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

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / evidence_core

Added value: +{
+  "description": "The canonical, signed core of the answer — the payload the signature covers.",
+  "type": "object"
+}

addedOutput schema / properties / factors

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

addedOutput schema / properties / identifier

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

addedOutput schema / properties / key_id

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / missing_fields

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

addedOutput schema / properties / name

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

Added value: +{
+  "description": "SHA-256 hex digest of the canonical evidence core.",
+  "type": "string"
+}

addedOutput schema / properties / profileVersion

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

addedOutput schema / properties / profile_version

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 / score

Added value: +{
+  "description": "The numeric score this tool returned.",
+  "type": "number"
+}

addedOutput schema / properties / signature

Added value: +{
+  "description": "The Ed25519 signature over the evidence core, base64-encoded.",
+  "type": "string"
+}

addedOutput schema / properties / signature_algorithm

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

addedOutput schema / properties / signedAt

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

addedOutput schema / properties / signed_at

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

addedOutput schema / properties / signed_by

Added value: +{
+  "description": "The key id that signed the answer.",
+  "type": "string"
+}

removedOutput schema / properties / status

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

addedOutput schema / properties / value

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

addedOutput schema / properties / weight

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

addedOutput schema / required

Added value: +[
+  "detail",
+  "evidence_core",
+  "output_sha256",
+  "signature"
+]

AddedOct 31, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the description's real contribution is the paid-call disclosure ('$0.5 USDC') and the return shape ('an object with 29 fields'), both of which are behavioral facts an agent needs before calling. No permissions, latency, or failure-mode context is given.

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?

Short and front-loaded on the routing decision, but it contains waste and broken fragments: 'from YOUR OWN.' is truncated, and '29 fields including asOf, as_of' is a redundant restatement that duplicates what the output schema already carries.

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?

The output schema exists, so describing the 29-field return object is unnecessary, while genuinely useful gaps remain: what an 'identifier' should be (agent id, host, endpoint), whether observations are required to get a meaningful answer, and what happens with the default empty as_of. For a 0-required-param, all-optional tool the description should clarify what a valid call looks like.

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 coverage is 100%, and the schema descriptions for identifier and observations are boilerplate ('The identifier this operation operates on'), so the schema does not fully explain them either. The description mentions asOf/as_of, but those are output fields rather than parameters, so it adds nothing for the three inputs. Baseline 3 applies.

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?

States a specific verb ('price the risk') and resource ('paying an unknown agent, endpoint or host'), and explicitly contrasts itself with assess_agent_verdict. The phrase 'from YOUR OWN' trails off and never resolves, leaving the perspective/scope slightly garbled, which keeps it from a 5.

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?

Names the alternative assess_agent_verdict and the condition that selects it ('for counterparty risk, not agent verdict'). It does not route against the many adjacent siblings (assess_endpoint_verdict, assess_service_verdict, get_counterparty_preflight/verify_counterparty_preflight), so the coverage of alternatives is partial.

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.