Synthex Forge — x402 Paid Agent Services

Assess Agent Verdict

assess_agent_verdict

Read-onlyIdempotent

Is this wallet safe to transact with right now?. use it rather than assess_counterparty_risk for agent verdict, not counterparty risk; an object with 30 fields including address, algorithm. $0.02 USDC.

Input Schema

Name	Required	Description	Default
`chain`	No	The chain this operation operates on. See the schema for its type and whether it is required.
`address`	Yes	The address this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`kind`	No	The `kind` field of the response.
`as_of`	No	The date the answer is computed as of.
`chain`	No	The `chain` field of the response.
`route`	No	The `route` field of the response.
`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.
`sha256`	No	The `sha256` field of the response.
`address`	No	The `address` field of the response.
`reasons`	No	The `reasons` field of the response.
`service`	No	The `service` field of the response.
`subject`	No	The `subject` field of the response.
`verdict`	Yes	The decision this tool returned.
`coverage`	No	How much of the underlying corpus the answer is based on.
`evidence`	No	The `evidence` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`last_seen`	No	The `last_seen` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`disclaimer`	No	The `disclaimer` field of the response.
`first_seen`	No	The `first_seen` field of the response.
`public_key`	No	The `public_key` field of the response.
`risk_flags`	No	The `risk_flags` field of the response.
`signed_over`	No	The `signed_over` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`counterparties`	No	The `counterparties` field of the response.
`profile_version`	No	Version of the answer profile.
`minimum_required`	No	The `minimum_required` field of the response.
`settlements_observed`	No	The `settlements_observed` field of the response.
`top_counterparty_share`	No	The `top_counterparty_share` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed32 schema fields changedOct 31, 2026

addedOutput schema / properties / address

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

addedOutput schema / properties / algorithm

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

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

addedOutput schema / properties / counterparties

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

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

addedOutput schema / properties / disclaimer

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

addedOutput schema / properties / evidence

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

addedOutput schema / properties / first_seen

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

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

addedOutput schema / properties / minimum_required

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

addedOutput schema / properties / output_sha256

Added value: +{
+  "description": "SHA-256 hex digest of the canonical evidence core.",
+  "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 / reasons

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

addedOutput schema / properties / risk_flags

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

addedOutput schema / properties / route

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

addedOutput schema / properties / service

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

addedOutput schema / properties / settlements_observed

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

addedOutput schema / properties / sha256

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

addedOutput schema / properties / signature

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

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

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

addedOutput schema / properties / top_counterparty_share

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

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

AddedOct 31, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful non-annotated context: a price of $0.02 USDC and an indication of a wide (~30 field) response. It omits anything about permissions, rate limits, or latency, and the output-shape note is partly 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?

It is short and front-loads the core question, then routing, output, and price in a sensible order. But the middle clause is a run-on fragment ("for agent verdict, not counterparty risk; an object with 30 fields...") that reads as truncated text and forces re-parsing, which undercuts an otherwise tight description.

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 and full parameter descriptions exist, so the description needn't explain return values, and it does supply price and an alternative. Still, given the dense crowd of `assess_*_verdict` siblings, it leaves unclear what signal decides "safe" and how it differs from assess_tool_verdict or get_agent_reputation.

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%, so both `address` and `chain` are already documented in structured form, which sets the baseline at 3. The description mentions "address" only incidentally as an output field and adds no format, defaults, or chain-selection semantics beyond 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 frames the tool as a question ("Is this wallet safe to transact with right now?") and names a sibling it is not, which helps, but it never states the operation in verb+resource form and drifts between "wallet" and the tool's "agent verdict" name. Against a family containing assess_endpoint_verdict, assess_service_verdict, assess_tool_verdict and assess_counterparty_risk, an agent cannot confidently pin down what object is actually being assessed.

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: use this rather than `assess_counterparty_risk` for agent verdict, not counterparty risk. That is a concrete alternative and condition. It does not address the other verdict-style siblings, so the exclusion set is only partially covered.

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.