Synthex Forge — x402 Paid Agent Services

Record Agent Memory

record_agent_memory

Destructive

Persist a budget-capped state version into a signed, reproducible memory vault. use it rather than get_agent_memory for agent memory specifically; an object with 23 fields including _, algorithm. $0.1 USDC.

Input Schema

Name	Required	Description
`key`	No	The key this operation operates on. See the schema for its type and whether it is required.
`owner`	No	The owner this operation operates on. See the schema for its type and whether it is required.
`value`	No	The value this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`_`	No	The `_` field of the response.
`key`	No	The `key` field of the response.
`kind`	No	The `kind` field of the response.
`note`	No	A note on how the answer was produced.
`owner`	No	The `owner` field of the response.
`value`	No	The `value` field of the response.
`detail`	Yes	Human-readable explanation of the verdict.
`sealed`	No	The `sealed` field of the response.
`sha256`	No	The `sha256` field of the response.
`stored`	No	The `stored` field of the response.
`verdict`	Yes	The decision this tool returned.
`version`	No	The `version` field of the response.
`signedBy`	No	The `signedBy` field of the response.
`algorithm`	No	The `algorithm` field of the response.
`stateHash`	No	The `stateHash` field of the response.
`ed25519Sig`	No	The `ed25519Sig` field of the response.
`recordedAt`	No	The `recordedAt` field of the response.
`observations`	No	The `observations` field of the response.
`publicKeyHex`	No	The `publicKeyHex` field of the response.
`verdictLevel`	No	The `verdictLevel` field of the response.
`prevStateHash`	No	The `prevStateHash` field of the response.
`canonicalSha256`	No	The `canonicalSha256` field of the response.
`reproducibility`	No	The `reproducibility` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed25 schema fields changedOct 31, 2026

addedOutput schema / properties / _

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

addedOutput schema / properties / algorithm

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

addedOutput schema / properties / canonicalSha256

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

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

addedOutput schema / properties / kind

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

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

addedOutput schema / properties / owner

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

addedOutput schema / properties / prevStateHash

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

addedOutput schema / properties / publicKeyHex

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

addedOutput schema / properties / recordedAt

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

addedOutput schema / properties / reproducibility

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

addedOutput schema / properties / sealed

Added value: +{
+  "description": "The `sealed` 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"
+}

addedOutput schema / properties / stateHash

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

removedOutput schema / properties / status

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

addedOutput schema / properties / stored

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

addedOutput schema / properties / value

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

addedOutput schema / properties / verdict

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

addedOutput schema / properties / verdictLevel

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

addedOutput schema / properties / version

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

addedOutput schema / required

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

AddedOct 31, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already disclose destructiveHint=true, idempotentHint=false, and openWorldHint=false, so the safety profile is largely covered. The description adds useful context beyond the annotations: the vault is signed and reproducible, the operation is budget-capped, it costs $0.1 USDC, and it mentions a 23-field return object. It still does not explain what existing state may be overwritten despite the destructive annotation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The main action is front-loaded and the description is short, but it contains awkward fragments such as 'an object with 23 fields including _, algorithm' and a stray cost sentence. The return-shape fragment is especially redundant because an output schema exists.

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?

The tool has annotations, an output schema, and full schema description coverage, which reduces what the description must carry. Still, for a paid destructive write operation, the description omits important operational context such as overwrite behavior and how the $0.1 USDC payment is handled.

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 baseline is 3. The description mentions persisting a state version but adds no meaningful semantics for key, owner, or value beyond what the schema already carries.

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 write action: persisting a state version into a signed, reproducible memory vault. It also names the sibling get_agent_memory, though the phrase 'budget-capped state version' and the fragment about 'an object with 23 fields' make the resource being written somewhat muddier than it should be.

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 explicitly mentions get_agent_memory as a related sibling and says to use this tool rather than that one for agent memory specifically, and it notes the $0.1 USDC cost. However, it does not clearly explain the when-to-use boundary between recording and retrieving memory, nor does it state prerequisites or exclusions.

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.