Synthex Forge — x402 Paid Agent Services

Get Agent Memory

get_agent_memory

Read-onlyIdempotent

Reading that durable memory back — continuity for an agent that must not forget. use it rather than record_agent_memory for agent memory specifically; an object with 21 fields including _, algorithm. $0.05 USDC.

Input Schema

Name	Required	Description	Default
`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.

Output Schema

Name	Required	Description
`_`	No	The `_` field of the response.
`key`	No	The `key` field of the response.
`note`	No	A note on how the answer was produced.
`found`	No	The `found` field of the response.
`owner`	No	The `owner` 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.
`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.
`checkedAt`	No	The `checkedAt` field of the response.
`stateHash`	No	The `stateHash` field of the response.
`ed25519Sig`	No	The `ed25519Sig` 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.

Changed23 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 / checkedAt

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

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

addedOutput schema / properties / key

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

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds useful context beyond annotations: durability/continuity, a concrete cost of $0.05 USDC, and a return object with 21 fields including `_, algorithm`.

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 description is short and front-loads purpose, but it is awkwardly phrased and the fragment "an object with 21 fields including _, algorithm" is cryptic. The cost and return-shape details are useful, but the structure is not clean.

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?

With a rich annotation set and an output schema present, the description supplies the key missing behavioral context: cost, return shape, and the alternative to `record_agent_memory`. Parameter semantics are left to the schema, which is fully covered.

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 `key` and `owner` are already documented in the schema. The description adds no additional parameter meaning, which is acceptable at baseline 3 when the schema carries parameter semantics.

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 action ("Reading") and resource ("durable memory" / "agent memory") and explicitly contrasts it with `record_agent_memory`. The phrasing "that durable memory" is slightly vague, and the cryptic return-field note weakens precision, but an agent can still identify what the tool does.

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 `record_agent_memory` for agent memory. It does not spell out broader when-not conditions, but the sibling routing is clear enough for selection.

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.