Synthex Forge — x402 Paid Agent Services

Check Data Usage Rights

check_data_usage_rights

Read-onlyIdempotent

What does this licence permit, per dimension?. use it rather than check_compliance_status for usage rights, not compliance status; an object with 19 fields including clause, clause_resolved. $0.05 USDC.

Input Schema

Name	Required	Description
`context`	No	Free-form context the operation needs but does not model as a structured field.
`dataset`	No	The dataset the operation concerns.
`licence_spdx`	No	The SPDX identifier of the licence.
`licence_text`	No	The full licence text.
`proposed_uses`	No	The uses the caller intends to make of the dataset.

Output Schema

Name	Required	Description
`gap`	No	The `gap` field of the response.
`type`	No	The `type` field of the response.
`clause`	No	The `clause` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`reader`	No	The `reader` field of the response.
`source`	No	The `source` field of the response.
`context`	No	The `context` field of the response.
`dataset`	No	The `dataset` field of the response.
`verdict`	Yes	The decision this tool returned.
`condition`	No	The `condition` field of the response.
`dimension`	No	The `dimension` field of the response.
`exception`	No	The `exception` field of the response.
`dimensions`	No	The `dimensions` field of the response.
`clause_source`	No	The `clause_source` field of the response.
`proposed_uses`	No	The `proposed_uses` field of the response.
`clause_resolved`	No	The `clause_resolved` field of the response.
`reader_available`	No	The `reader_available` field of the response.
`licence_identifier`	No	The `licence_identifier` field of the response.
`licence_text_supplied`	No	The `licence_text_supplied` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedOct 31, 2026

addedOutput schema / properties / clause

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

addedOutput schema / properties / clause_resolved

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

addedOutput schema / properties / clause_source

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

addedOutput schema / properties / condition

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

addedOutput schema / properties / context

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

addedOutput schema / properties / dataset

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / dimension

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

addedOutput schema / properties / dimensions

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

addedOutput schema / properties / exception

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

addedOutput schema / properties / gap

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

addedOutput schema / properties / licence_identifier

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

addedOutput schema / properties / licence_text_supplied

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

addedOutput schema / properties / proposed_uses

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

addedOutput schema / properties / reader

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

addedOutput schema / properties / reader_available

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

addedOutput schema / properties / source

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

removedOutput schema / properties / status

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

addedOutput schema / properties / type

Added value: +{
+  "description": "The `type` 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",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds real value beyond them: a per-call price of $0.05 USDC and the shape of the response (19 fields incl. clause, clause_resolved). It still says nothing about how truncated or ambiguous licence text is handled.

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

Conciseness4/5

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

Very short and front-loaded with the core question and the alternative statement. The stray punctuation ('per dimension?.') and the fragment-style clauses make it slightly harder to parse, but no sentence is wasted.

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?

An output schema exists, so return-value explanation is optional, and the tool is a read-only single-shot analysis. Cost and routing are covered; the only real gap is guidance on which of the optional licence inputs to supply.

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%, so the five parameters are already documented in structured form; the description adds no param-level meaning. 'Per dimension' loosely hints that proposed_uses drives the dimensional breakdown, but that is inference, not specification.

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 concrete analytical question (what the licence permits, broken out per dimension) rather than restating the name, and names the sibling it replaces (check_compliance_status). It does not differentiate from the other licence-ish siblings (check_licence_status, verify_licence_status), so it stops short of 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?

Gives an explicit routing rule: use this for usage rights, not compliance status, pointing at the alternative by name. No guidance on when-not to use it relative to the other licence siblings, and no stated prerequisites (e.g., whether licence_text or licence_spdx is needed).

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.