Synthex Forge — x402 Paid Agent Services

Issue Nav Attestation

issue_nav_attestation

Destructive

A signed NAV attestation for agent treasuries. use it rather than issue_decision_attestation for nav attestation, not attestation; an object with 60 fields including amount, asOf. $10 USDC.

Input Schema

Name	Required	Description	Default
`cash`	No	The cash this operation operates on. See the schema for its type and whether it is required.
`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.
`currency`	No	The currency this operation operates on. See the schema for its type and whether it is required.	USD
`positions`	No	The positions the operation evaluates.
`liabilities`	No	The liabilities this operation operates on. See the schema for its type and whether it is required.
`methodology`	No	The methodology this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`fx`	No	The `fx` field of the response.
`due`	No	The `due` field of the response.
`nav`	No	The `nav` field of the response.
`asOf`	No	The `asOf` field of the response.
`kind`	No	The `kind` field of the response.
`mark`	No	The `mark` field of the response.
`note`	No	A note on how the answer was produced.
`as_of`	No	The date the answer is computed as of.
`index`	No	The `index` field of the response.
`label`	No	The `label` field of the response.
`stale`	No	The `stale` field of the response.
`amount`	No	The `amount` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`key_id`	No	The `key_id` field of the response.
`reason`	No	Why the verdict was reached.
`source`	No	The `source` field of the response.
`symbol`	No	The `symbol` field of the response.
`licence`	No	The `licence` field of the response.
`perLine`	No	The `perLine` field of the response.
`pricing`	No	The `pricing` field of the response.
`verdict`	Yes	The decision this tool returned.
`currency`	No	The `currency` field of the response.
`fx_table`	No	The `fx_table` field of the response.
`per_line`	No	The `per_line` field of the response.
`quantity`	No	The `quantity` field of the response.
`signedAt`	No	The `signedAt` field of the response.
`netAssets`	No	The `netAssets` field of the response.
`ratesUsed`	No	The `ratesUsed` 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.
`fx_licence`	No	The `fx_licence` field of the response.
`mark_as_of`	No	The `mark_as_of` field of the response.
`net_assets`	No	The `net_assets` field of the response.
`public_key`	No	The `public_key` field of the response.
`staleMarks`	No	The `staleMarks` field of the response.
`attribution`	No	The `attribution` field of the response.
`grossAssets`	No	The `grossAssets` field of the response.
`liabilities`	No	The `liabilities` field of the response.
`mark_source`	No	The `mark_source` field of the response.
`methodology`	No	The `methodology` field of the response.
`stale_marks`	No	The `stale_marks` field of the response.
`coverageGaps`	No	The `coverageGaps` field of the response.
`gross_assets`	No	The `gross_assets` field of the response.
`priced_lines`	No	The `priced_lines` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`evidence_core`	Yes	The canonical, signed core of the answer — the payload the signature covers.
`fx_rates_used`	No	The `fx_rates_used` field of the response.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`fx_attribution`	No	The `fx_attribution` field of the response.
`missing_fields`	No	The `missing_fields` field of the response.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`mark_age_minutes`	No	The `mark_age_minutes` field of the response.
`totalLiabilities`	No	The `totalLiabilities` field of the response.
`total_liabilities`	No	The `total_liabilities` field of the response.
`valuation_instant`	No	The `valuation_instant` field of the response.
`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.
`stale_after_minutes`	No	The `stale_after_minutes` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed62 schema fields changedOct 31, 2026

addedOutput schema / properties / amount

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

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

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

addedOutput schema / properties / coverage_gaps

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

addedOutput schema / properties / currency

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

addedOutput schema / properties / detail

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

addedOutput schema / properties / due

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

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

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

addedOutput schema / properties / fx_attribution

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

addedOutput schema / properties / fx_licence

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

addedOutput schema / properties / fx_rates_used

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

addedOutput schema / properties / fx_table

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

addedOutput schema / properties / grossAssets

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

addedOutput schema / properties / gross_assets

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

addedOutput schema / properties / index

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

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

addedOutput schema / properties / liabilities

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

addedOutput schema / properties / licence

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

addedOutput schema / properties / mark

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

addedOutput schema / properties / mark_age_minutes

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

addedOutput schema / properties / mark_as_of

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

addedOutput schema / properties / mark_source

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

addedOutput schema / properties / methodology

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

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

addedOutput schema / properties / nav

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

addedOutput schema / properties / netAssets

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

addedOutput schema / properties / net_assets

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

Added value: +{
+  "description": "SHA-256 hex digest of the canonical evidence core.",
+  "type": "string"
+}

addedOutput schema / properties / perLine

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

addedOutput schema / properties / per_line

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

addedOutput schema / properties / priced_lines

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

addedOutput schema / properties / pricing

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

addedOutput schema / properties / public_key

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

addedOutput schema / properties / quantity

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

addedOutput schema / properties / ratesUsed

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

addedOutput schema / properties / reason

Added value: +{
+  "description": "Why the verdict was reached.",
+  "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"
+}

addedOutput schema / properties / source

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

addedOutput schema / properties / stale

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

addedOutput schema / properties / staleMarks

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

addedOutput schema / properties / stale_after_minutes

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

addedOutput schema / properties / stale_marks

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

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

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

addedOutput schema / properties / total_liabilities

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

addedOutput schema / properties / valuation_instant

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

AddedOct 31, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true, non-idempotent, and closed-world, so the safety profile is covered; the description does not contradict that, since issuing/signing is a write. It adds genuinely useful context the annotations don't carry — the $10 USDC price and the shape of the returned signed object — but says nothing about why it is destructive, what must exist beforehand, or whether the charge applies on failure.

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?

It is short, but the structure is broken: semicolon-joined fragments and an ungrammatical clause ("use it rather than `issue_decision_attestation` for nav attestation, not attestation") force re-reading. Brevity does not earn credit when the sentences are malformed.

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?

Output schema is present, so the "60 fields" line is optional rather than required, and annotations carry the safety and concurrency profile, which lowers the descriptive burden. What remains thin is operational framing for a destructive, paid, non-idempotent call — prerequisites and failure/charge semantics — but the core purpose, cost, alternative, and return shape are all stated.

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 six inputs (cash, as_of, currency, positions, liabilities, methodology) are already documented; baseline 3 applies. The description's mention of "amount, asOf" describes return fields rather than inputs and introduces mild noise, since the schema uses `as_of` and has no `amount` parameter.

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 opening clause, "A signed NAV attestation for agent treasuries," does give a specific verb and resource, enough to separate it from `issue_uptime_attestation` or `issue_agent_credential`. But the remainder ("for nav attestation, not attestation") is garbled and partly undercuts the clarity it just established.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It does name one explicit alternative, `issue_decision_attestation`, and says to prefer this tool for NAV attestations, which is real routing guidance. However there are many other attestation siblings (`issue_attestation`, `issue_attestation_receipt`, `issue_readiness_attestation`) and no guidance on when those apply, and the phrase "not attestation" is confusing rather than a constraint.

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.