Synthex Forge — x402 Paid Agent Services

Accept Task Deliverable

accept_task_deliverable

Read-onlyIdempotent

Grade the observations. use it rather than evaluate_deliverable_acceptance for task deliverable, not deliverable acceptance; an object with 39 fields including absent_observation_rule, canonicalization. $0.25 USDC.

Input Schema

Name	Required	Description	Default
`spec`	No	The spec this operation operates on. See the schema for its type and whether it is required.
`observed`	No	The observed this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`id`	No	The `id` field of the response.
`llm`	No	The `llm` field of the response.
`fail`	No	The `fail` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`pass`	No	The `pass` field of the response.
`clock`	No	The `clock` field of the response.
`kinds`	No	The `kinds` field of the response.
`score`	No	The numeric score this tool returned.
`total`	No	The `total` field of the response.
`counts`	No	The `counts` field of the response.
`key_id`	No	The `key_id` field of the response.
`profile`	No	The `profile` field of the response.
`results`	No	The results the operation produced.
`verdict`	Yes	The decision this tool returned.
`criteria`	No	The `criteria` field of the response.
`expected`	No	The `expected` field of the response.
`observed`	No	The `observed` field of the response.
`verdicts`	No	The `verdicts` field of the response.
`signature`	Yes	The Ed25519 signature over the evidence core, base64-encoded.
`signed_by`	No	The key id that signed the answer.
`tolerance`	No	The `tolerance` field of the response.
`public_key`	No	The `public_key` field of the response.
`methodology`	No	The `methodology` field of the response.
`coverageGaps`	No	The `coverageGaps` field of the response.
`undetermined`	No	The `undetermined` 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.
`output_sha256`	Yes	SHA-256 hex digest of the canonical evidence core.
`missing_fields`	No	The `missing_fields` field of the response.
`profileVersion`	No	Version of the answer profile.
`profile_version`	No	Version of the answer profile.
`canonicalization`	No	The canonicalisation rule the digest was computed under.
`string_comparison`	No	The `string_comparison` field of the response.
`tolerance_applied`	No	The `tolerance_applied` 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.
`absent_observation_rule`	No	The `absent_observation_rule` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed41 schema fields changedOct 31, 2026

addedOutput schema / properties / absent_observation_rule

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

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

addedOutput schema / properties / counts

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

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

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

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

addedOutput schema / properties / fail

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

addedOutput schema / properties / id

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

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

addedOutput schema / properties / llm

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

Added value: +{
+  "description": "A note on how the answer was produced.",
+  "type": "string"
+}

addedOutput schema / properties / observed

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

addedOutput schema / properties / output_sha256

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

addedOutput schema / properties / pass

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

addedOutput schema / properties / profile

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

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

addedOutput schema / properties / results

Added value: +{
+  "description": "The results the operation produced.",
+  "items": {
+    "description": "One record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / score

Added value: +{
+  "description": "The numeric score this tool returned.",
+  "type": "number"
+}

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

Added value: +{
+  "description": "The key id that signed the answer.",
+  "type": "string"
+}

removedOutput schema / properties / status

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

addedOutput schema / properties / string_comparison

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

addedOutput schema / properties / tolerance

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

addedOutput schema / properties / tolerance_applied

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

addedOutput schema / properties / total

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

addedOutput schema / properties / undetermined

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / verdicts

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

addedOutput schema / required

Added value: +[
+  "evidence_core",
+  "output_sha256",
+  "signature",
+  "verdict"
+]

AddedOct 31, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, non-destructive operation, so the description does not need to restate safety. It adds a cost signal ('$0.25 USDC') and a hint about the returned object having 39 fields, but this return-shape information is partly redundant with the output schema and the description does not explain permissions or rate limits.

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 description is short but poorly structured: it is a run-on sentence mixing purpose, sibling routing, return-shape hints, and pricing. The key routing instruction is buried mid-sentence, and the '39 fields' detail is not front-loaded or clearly connected to the output schema.

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 an output schema present and full schema description coverage, the description does not need to explain return values in detail. Still, for a tool whose name implies acceptance but whose description says 'grade the observations', the definition leaves the actual grading/acceptance semantics and the meaning of `spec` versus `observed` under-explained.

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 parameters are structurally documented, and baseline 3 applies. However, the schema descriptions are generic ('The spec this operation operates on'), and the tool description does not compensate by explaining what `spec` or `observed` should contain beyond the vague reference to observations.

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?

The description states a specific verb and resource ('Grade the observations') and explicitly contrasts the tool with the sibling `evaluate_deliverable_acceptance`, saying to use this one for task deliverables. That sibling differentiation is useful, though the phrasing is awkward and does not fully explain what 'grading observations' means in the context of accepting a task deliverable.

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 gives an explicit alternative: use this rather than `evaluate_deliverable_acceptance` for task deliverable, not deliverable acceptance. The condition is present but compressed into a confusing clause, and there is no broader guidance about prerequisites or when not to use this tool.

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.