Synthex Forge — x402 Paid Agent Services

Verify Prepaid Capacity

verify_prepaid_capacity

Read-onlyIdempotent

verify a pass token's signature, scope and expiry. use it rather than create_prepaid_capacity for prepaid capacity specifically; an object with 13 fields including calls_remaining, calls_total.

Input Schema

Name	Required	Description	Default
`pass_token`	Yes	The compact pass_token issued by POST /v1/pass/purchase.

Output Schema

Name	Required	Description
`valid`	Yes	Whether the artifact verified.
`claims`	No	The `claims` field of the response.
`reason`	No	Why the verdict was reached.
`pass_id`	No	The `pass_id` field of the response.
`consumed`	No	The `consumed` field of the response.
`checkedAt`	No	The `checkedAt` field of the response.
`issued_at`	No	The `issued_at` field of the response.
`expires_at`	No	The `expires_at` field of the response.
`calls_total`	No	The `calls_total` field of the response.
`route_scope`	No	The `route_scope` field of the response.
`scopeCovers`	No	The `scopeCovers` field of the response.
`scopeMaxUsd`	No	The `scopeMaxUsd` field of the response.
`calls_remaining`	No	The `calls_remaining` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed15 schema fields changedOct 31, 2026

addedOutput schema / properties / calls_remaining

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

addedOutput schema / properties / calls_total

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

addedOutput schema / properties / checkedAt

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

addedOutput schema / properties / claims

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

addedOutput schema / properties / consumed

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

addedOutput schema / properties / expires_at

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

addedOutput schema / properties / issued_at

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

addedOutput schema / properties / pass_id

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "type": "string"
+}

addedOutput schema / properties / route_scope

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

addedOutput schema / properties / scopeCovers

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

addedOutput schema / properties / scopeMaxUsd

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

removedOutput schema / properties / status

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

addedOutput schema / properties / valid

Added value: +{
+  "description": "Whether the artifact verified.",
+  "type": "boolean"
+}

addedOutput schema / required
```
Added value: +[
+  "valid"
+]
```

AddedOct 31, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds what is validated (signature, scope, expiry) plus a hint at the return shape, but it never says what happens on failure — whether an invalid/expired token raises an error or returns a negative result — which is the key behavioral question for a verify tool.

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?

Two short sentences, front-loaded with what is verified. The second half spends words enumerating return fields ('13 fields including calls_remaining, calls_total') that are already carried by the output schema, so it is not entirely waste-free.

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 values need not be described — yet the description describes them anyway while omitting failure semantics and any note on token freshness/clock skew. Adequate for a single-parameter read tool, but the description's emphasis is misplaced relative to the actual 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?

Only one parameter exists and schema description coverage is 100%, with the schema documenting that the compact pass_token comes from POST /v1/pass/purchase. The description adds nothing about the token format or validation expectations, so the 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?

Names a specific verb (verify) plus the exact things checked — signature, scope, expiry — and explicitly contrasts with the create_prepaid_capacity sibling. However, it only differentiates itself from one sibling in a family of ~30 verify_* tools, and the phrase 'for prepaid capacity specifically' is slightly garbled and reads as a contrast of operation type rather than resource.

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?

The description explicitly names the alternative (create_prepaid_capacity) and implies this tool covers the verification side rather than issuance. There are no when-not conditions (e.g., what to do with an already-verified or expired token), but the create-vs-verify routing is clear.

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.