Synthex Forge — x402 Paid Agent Services

Verify Market History

verify_market_history

Read-onlyIdempotent

re-verify a signed market-history manifest. use it rather than verify_c2pa_provenance for market history, not c2pa provenance; an object with 5 fields including reason, rows_match.

Input Schema

Name	Required	Description	Default
`series`	Yes	Must be an object. The handler rejects a null or non-object value with 400 `bad_request`.
`manifest`	Yes	Must be an object. The handler rejects a null or non-object value with 400 `bad_request`.

Output Schema

Name	Required	Description
`valid`	Yes	Whether the artifact verified.
`reason`	No	Why the verdict was reached.
`rows_match`	No	The `rows_match` field of the response.
`sha256_match`	No	The `sha256_match` field of the response.
`signature_valid`	No	The `signature_valid` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 31, 2026

addedOutput schema / properties / reason

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

addedOutput schema / properties / rows_match

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

addedOutput schema / properties / sha256_match

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

addedOutput schema / properties / signature_valid

Added value: +{
+  "description": "The `signature_valid` 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.8/5.0

Behavior3/5

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

Annotations already carry the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's burden is lighter. It usefully implies a structured rather than thrown result by mentioning a `reason` field, hinting at failure semantics, but it never says whether a failed verification returns an error or a populated reason, nor anything about signature/source requirements.

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 with the action front-loaded and the sibling routing second – efficient and skimmable. The trailing output-shape fragment is cryptic and largely redundant with the existing output schema, so it is the one part that does not fully earn its place.

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?

With a rich output schema and complete annotations, the description is close to sufficient. The remaining gap is the inputs: for a tool with two required nested objects, an agent still cannot tell what a valid `series` or `manifest` looks like or which sibling (`get_market_history`, `get_market_history_bulk`, `create_signed_data_snapshot`) produces a signed manifest to feed in.

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 baseline 3 applies. However, both nested object schemas only contain a type guard ('Must be an object... 400 bad_request') and say nothing about the internal structure of `series` or `manifest`, and the description does not fill that gap. The '5 fields including reason, rows_match' clause describes the response, not the two required inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 're-verify a signed market-history manifest.' It also names the sibling it must not be confused with (`verify_c2pa_provenance`), so an agent can route correctly on the first read.

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?

Explicitly routes the agent away from `verify_c2pa_provenance` for market-history work, which is the key disambiguation among ~150 siblings. It does not state prerequisites (that the manifest must be signed, or which tool produces one) or when verification should be skipped, so it stops short of full when/when-not guidance.

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.