Synthex Forge — x402 Paid Agent Services

Evaluate Financial Precision

evaluate_financial_precision

Destructive

Exact... use it rather than create_attested_financial_evidence for financial precision, not attested financial evidence; an object with 46 fields including algorithm, amortisationFinalPaymentPolicy. $0.01 USDC.

Input Schema

Name	Required	Description
`params`	No	The operands of the operation.
`operation`	No	The operation to perform.
`conventions`	No	The rounding and day-count conventions to apply.
`evaluatedAt`	No	The moment the result was computed, as an ISO-8601 timestamp.

Output Schema

Name	Required	Description
`ok`	Yes	Whether the operation succeeded.
`code`	No	The `code` field of the response.
`note`	No	A note on how the answer was produced.
`checks`	No	The individual checks that were run.
`detail`	Yes	Human-readable explanation of the verdict.
`reason`	No	Why the verdict was reached.
`result`	No	The `result` field of the response.
`sha256`	No	The `sha256` field of the response.
`verdict`	Yes	The decision this tool returned.
`calendar`	No	The `calendar` field of the response.
`findings`	No	The `findings` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`assurance`	No	The `assurance` field of the response.
`irrMethod`	No	The `irrMethod` field of the response.
`operation`	No	The `operation` field of the response.
`arithmetic`	No	The `arithmetic` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`moneyScale`	No	The `moneyScale` field of the response.
`checksTotal`	No	The `checksTotal` field of the response.
`conventions`	No	The `conventions` field of the response.
`outputScale`	No	The `outputScale` field of the response.
`tickTieRule`	No	The `tickTieRule` field of the response.
`checks_total`	No	The `checks_total` field of the response.
`evaluated_at`	No	The `evaluated_at` field of the response.
`evidenceCore`	No	The `evidenceCore` field of the response.
`irrTolerance`	No	The `irrTolerance` field of the response.
`paymentScale`	No	The `paymentScale` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`roundingMode`	No	The `roundingMode` field of the response.
`coverage_gaps`	No	The `coverage_gaps` field of the response.
`checksObserved`	No	The `checksObserved` field of the response.
`profileVersion`	No	Version of the answer profile.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`checks_observed`	No	The `checks_observed` field of the response.
`profile_version`	No	Version of the answer profile.
`reproducibility`	No	The `reproducibility` field of the response.
`fxRateDefinition`	No	The `fxRateDefinition` field of the response.
`irrMaxIterations`	No	The `irrMaxIterations` field of the response.
`workingPrecision`	No	The `workingPrecision` field of the response.
`authoritativeField`	No	The `authoritativeField` field of the response.
`irrMultiRootPolicy`	No	The `irrMultiRootPolicy` field of the response.
`irrRootCompleteness`	No	The `irrRootCompleteness` field of the response.
`amortisationRateBasis`	No	The `amortisationRateBasis` field of the response.
`amortisationPaymentTiming`	No	The `amortisationPaymentTiming` field of the response.
`amortisationFinalPaymentPolicy`	No	The `amortisationFinalPaymentPolicy` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed48 schema fields changedOct 31, 2026

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / amortisationFinalPaymentPolicy

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

addedOutput schema / properties / amortisationPaymentTiming

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

addedOutput schema / properties / amortisationRateBasis

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

addedOutput schema / properties / arithmetic

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

addedOutput schema / properties / assurance

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

addedOutput schema / properties / authoritativeField

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

addedOutput schema / properties / calendar

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

addedOutput schema / properties / canonicalSha256

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

addedOutput schema / properties / checks

Added value: +{
+  "description": "The individual checks that were run.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / checksObserved

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

addedOutput schema / properties / checksTotal

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

addedOutput schema / properties / checks_observed

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

addedOutput schema / properties / checks_total

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

addedOutput schema / properties / code

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

addedOutput schema / properties / conventions

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

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

addedOutput schema / properties / ed25519Sig

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

addedOutput schema / properties / evaluated_at

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

addedOutput schema / properties / evidenceCore

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

addedOutput schema / properties / findings

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

addedOutput schema / properties / fxRateDefinition

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

addedOutput schema / properties / irrMaxIterations

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

addedOutput schema / properties / irrMethod

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

addedOutput schema / properties / irrMultiRootPolicy

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

addedOutput schema / properties / irrRootCompleteness

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

addedOutput schema / properties / irrTolerance

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

addedOutput schema / properties / moneyScale

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

Added value: +{
+  "description": "Whether the operation succeeded.",
+  "type": "boolean"
+}

addedOutput schema / properties / operation

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

addedOutput schema / properties / outputScale

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

addedOutput schema / properties / paymentScale

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

addedOutput schema / properties / profileVersion

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / profile_version

Added value: +{
+  "description": "Version of the answer profile.",
+  "type": "string"
+}

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / reason

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / result

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

addedOutput schema / properties / roundingMode

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

addedOutput schema / properties / sha256

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

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

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

addedOutput schema / properties / verdict

Added value: +{
+  "description": "The decision this tool returned.",
+  "type": "string"
+}

addedOutput schema / properties / workingPrecision

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

addedOutput schema / required

Added value: +[
+  "detail",
+  "ok",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations declare destructiveHint=true and idempotentHint=false, and the description neither confirms nor contradicts this, so no contradiction is flagged. It adds two pieces of context annotations do not cover — a $0.01 USDC cost and an outline of the 46-field result object — but it leaves the destructive semantics completely unexplained.

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?

The text is a run-on, semicolon-separated jumble that begins mid-thought with "Exact..." and buries the one useful routing clause after the fragment. It is short but not front-loaded, and the ellipsis signals a truncated definition rather than deliberate economy.

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

Completeness2/5

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

An output schema exists and all four parameters are documented, so those burdens are light, but the description still never says what computation is performed, what `operation` values mean, or why a pure-seeming evaluation carries destructiveHint=true. For a priced, allegedly destructive tool, that is a meaningful gap.

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 `params`, `operation`, `conventions`, and `evaluatedAt` are already documented in the schema. The description references algorithmic fields like `amortisationFinalPaymentPolicy` but does not map them to parameters or clarify operand structure, so nothing is added beyond the baseline.

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 description opens with the fragment "Exact..." and never states a clear verb+resource; the actual purpose (evaluating financial precision) is only inferable from the tool name. It does, however, sharpen the boundary against `create_attested_financial_evidence`, so an agent can narrow the choice even without a clean purpose statement.

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 explicitly names the alternative (`create_attested_financial_evidence`) and states the selecting condition: use this for financial precision, not attested financial evidence. That is real routing guidance, though it stops short of describing preconditions or when the tool should not be used at all.

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.