Synthex Forge — x402 Paid Agent Services

Assess Mandate Compliance

assess_mandate_compliance

Destructive

A signed, dated compliance certificate an allocator can actually. use it rather than assess_spend_anomaly for mandate compliance, not spend anomaly; an object with 29 fields including actual, asOf. $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.
`mandate`	No	The mandate this operation operates on. See the schema for its type and whether it is required.
`portfolio`	No	The portfolio 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.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`rule`	No	The rule or criteria that decided the verdict.
`as_of`	No	The date the answer is computed as of.
`class`	No	The `class` field of the response.
`limit`	No	The `limit` field of the response.
`actual`	No	The `actual` field of the response.
`checks`	No	The individual checks that were run.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`result`	No	The `result` field of the response.
`symbol`	No	The `symbol` field of the response.
`weight`	No	The `weight` field of the response.
`verdict`	Yes	The decision this tool returned.
`breaches`	No	The `breaches` 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.
`public_key`	No	The `public_key` 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.
`liquidity_score`	No	The `liquidity_score` field of the response.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`methodologyVersion`	No	The `methodologyVersion` field of the response.
`methodology_version`	No	Version of the method that produced the answer.
`signature_algorithm`	No	The `signature_algorithm` field of the response.
`indeterminate_reasons`	No	The `indeterminate_reasons` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed31 schema fields changedOct 31, 2026

addedOutput schema / properties / actual

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

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

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

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / class

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

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

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

addedOutput schema / properties / liquidity_score

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

addedOutput schema / properties / methodologyVersion

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

addedOutput schema / properties / methodology_version

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

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

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

addedOutput schema / properties / result

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

addedOutput schema / properties / rule

Added value: +{
+  "description": "The rule or criteria that decided the verdict.",
+  "type": "string"
+}

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

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

addedOutput schema / properties / verdict

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

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",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

B3.1/5.0

Behavior3/5

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

It contributes two genuinely useful facts annotations don't carry: the result is a signed, dated certificate, and the call costs $5 USDC. However, annotations declare destructiveHint=true and readOnlyHint=false, and the description frames this as producing a certificate with no mention of any state change or destructive effect, leaving the agent unable to reconcile the two.

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?

The content is short but structurally broken: the first sentence is a sentence fragment and the uses of 'it' have no antecedent. The key routing information is buried in a run-on clause after the broken opening.

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 return shape need not be explained, and cost plus certificate nature are covered. But for a tool annotated destructive and non-idempotent, the description says nothing about side effects, repeat-call behavior, or what mandate/portfolio inputs are required — leaving real gaps.

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%, including the important 'as_of' reproducibility note, so the schema already carries parameter meaning. The description adds nothing about mandate, portfolio, or observations; baseline 3 applies.

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 domain (mandate compliance) and says it returns a signed, dated compliance certificate, which an agent can connect to the tool name. But the opening sentence is a broken fragment ('an allocator can actually.') so the actual action — assess a mandate against a portfolio and observations — is never stated cleanly.

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 it rather than `assess_spend_anomaly` for mandate compliance, not spend anomaly.' That is a direct when-to-use / when-not-to-use signal. It gives no other prerequisites or context about when a compliance assessment is warranted.

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.