Synthex Forge — x402 Paid Agent Services

Check Compliance Status

check_compliance_status

Destructive

Compliance Check. use it rather than check_licence_status for compliance status, not licence status; an object with 34 fields including algorithm, applicable_obligations. $1 USDC.

Input Schema

Name	Required	Description	Default
`name`	No	The name this operation operates on. See the schema for its type and whether it is required.	AI use case
`users`	No	The users this operation operates on. See the schema for its type and whether it is required.
`sector`	No	The sector this operation operates on. See the schema for its type and whether it is required.
`purpose`	No	The purpose this operation operates on. See the schema for its type and whether it is required.
`category`	No	The category this operation operates on. See the schema for its type and whether it is required.
`provider`	No	The provider this operation operates on. See the schema for its type and whether it is required.
`data_types`	No	The data types this operation operates on. See the schema for its type and whether it is required.
`description`	No	The description this operation operates on. See the schema for its type and whether it is required.
`custom_details`	No	The custom details 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.
`name`	No	The `name` field of the response.
`note`	No	A note on how the answer was produced.
`tier`	No	The `tier` field of the response.
`asset`	No	The `asset` field of the response.
`label`	No	The `label` field of the response.
`users`	No	The `users` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sector`	No	The `sector` field of the response.
`sha256`	No	The `sha256` field of the response.
`framing`	No	The `framing` field of the response.
`purpose`	No	The `purpose` field of the response.
`receipt`	No	The `receipt` field of the response.
`category`	No	The `category` field of the response.
`provider`	No	The `provider` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`rationale`	No	The `rationale` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`assessedAt`	No	The `assessedAt` field of the response.
`assessment`	No	The `assessment` field of the response.
`data_types`	No	The `data_types` field of the response.
`disclaimer`	No	The `disclaimer` field of the response.
`references`	No	The `references` field of the response.
`description`	No	The `description` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`risk_register`	No	The `risk_register` field of the response.
`custom_details`	No	The `custom_details` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.
`verificationHint`	No	The `verificationHint` field of the response.
`assessment_summary`	No	The `assessment_summary` field of the response.
`risk_classification`	No	The `risk_classification` field of the response.
`applicable_obligations`	No	The `applicable_obligations` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed36 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / applicable_obligations

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

addedOutput schema / properties / assessedAt

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

addedOutput schema / properties / assessment

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

addedOutput schema / properties / assessment_summary

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

addedOutput schema / properties / asset

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / category

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

addedOutput schema / properties / custom_details

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

addedOutput schema / properties / data_types

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

addedOutput schema / properties / description

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

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

addedOutput schema / properties / kind

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

addedOutput schema / properties / label

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

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / purpose

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

addedOutput schema / properties / rationale

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

addedOutput schema / properties / receipt

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

addedOutput schema / properties / references

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / risk_classification

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

addedOutput schema / properties / risk_register

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

addedOutput schema / properties / sector

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

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

removedOutput schema / properties / status

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

addedOutput schema / properties / tier

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

addedOutput schema / properties / users

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

addedOutput schema / properties / verificationHint

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

B3.4/5.0

Behavior2/5

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

It adds two things annotations cannot: the call costs $1 USDC and returns an object with 34 fields including algorithm and applicable_obligations. However, annotations declare readOnlyHint=false, destructiveHint=true and idempotentHint=false, while the description frames the operation as a plain 'Check' — an agent could easily read this as a harmless read and never learn what is destructive, what is consumed besides the $1, or that repeated calls are not idempotent (and each may cost again).

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, but it is a single run-on sentence chaining four unrelated ideas (purpose, sibling routing, return shape, price) with semicolons, so nothing is clearly front-loaded beyond the two-word 'Compliance Check'. The return-shape detail is largely redundant given an output schema exists.

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

Completeness4/5

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

Annotations and an output schema carry most of the structural burden, and the description covers the routing decision and the price — the two things structured data does not. The remaining gap is the unexplained destructive/non-idempotent behavior for something the name calls a 'check'.

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 nominally 100%, so the baseline of 3 applies. The description contributes nothing about the nine inputs (name, users, sector, purpose, category, provider, data_types, description, custom_details), all of which are optional with empty-string defaults and boilerplate schema prose, so the agent gets no guidance on which fields actually matter or how they affect the result.

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 resource (compliance status) and verb (check), and explicitly separates it from the nearest sibling, check_licence_status, which is a real differentiation an agent can act on. It stops short of saying which compliance domain applies (the 'AI use case' default in the schema hints at AI-governance compliance, but the prose never says so).

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 either/or rule: use this rather than check_licence_status for compliance status, not licence status. That is a genuine routing instruction with an exclusion. It does not say what inputs are required to get a meaningful result or what preconditions (e.g., the payment) must hold before calling.

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.