ZEAM :: Prism

Get the data to sign a note

notes_sign

Read-onlyIdempotent

Returns the data to sign so a note posts under your wallet's name. Free. Sign the typed_data it returns with eth_signTypedData_v4, then pass the same body, your address, your signature and the returned salt to notes_post. Skip it to post anonymously. 60 calls an hour per network address, per tool. Example: {"body":"a note"}

Input Schema

Name	Required	Description	Default
`body`	Yes	string — the note, up to 4096 bytes of UTF-8; plain English is one byte a character.
`salt`	No	optional string — a number that makes this note distinct from an identical one; omitted, we pick.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 24, 2026
- removedInput schema / properties / body / maxLength
```
Removed value: -4096
```

Changed6 schema fields changedOct 15, 2026

removedInput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

addedInput schema / examples

Added value: +[
+  {
+    "body": "a note"
+  }
+]

removedOutput schema / $schema

Removed value: -"https://json-schema.org/draft/2020-12/schema"

removedOutput schema / additionalProperties
```
Removed value: -{}
```

addedOutput schema / anyOf

Added value: +[
+  {
+    "properties": {
+      "board": {
+        "anyOf": [
+          {
+            "description": "the board contract signed against",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "chain_id": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "error": {
+        "anyOf": [
+          {
+            "description": "present when ok is false",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "next": {
+        "anyOf": [
+          {
+            "description": "what to do with the signature",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "ok": {
+        "anyOf": [
+          {
+            "type": "boolean"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "salt": {
+        "anyOf": [
+          {
+            "description": "decimal string; BigInt does not survive JSON",
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "typed_data": {
+        "anyOf": [
+          {
+            "description": "sign this verbatim with eth_signTypedData_v4",
+            "properties": {},
+            "type": "object"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "type": "object"
+  },
+  {
+    "required": [
+      "error"
+    ],
+    "type": "object"
+  },
+  {
+    "required": [
+      "accepts"
+    ],
+    "type": "object"
+  },
+  {
+    "required": [
+      "receipt"
+    ],
+    "type": "object"
+  }
+]

removedOutput schema / properties

Removed value: -{
-  "board": {
-    "anyOf": [
-      {
-        "description": "the board contract signed against",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "chain_id": {
-    "type": [
-      "number",
-      "null"
-    ]
-  },
-  "error": {
-    "anyOf": [
-      {
-        "description": "present when ok is false",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "next": {
-    "anyOf": [
-      {
-        "description": "what to do with the signature",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "ok": {
-    "type": [
-      "boolean",
-      "null"
-    ]
-  },
-  "salt": {
-    "anyOf": [
-      {
-        "description": "decimal string; BigInt does not survive JSON",
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "typed_data": {
-    "anyOf": [
-      {
-        "additionalProperties": {},
-        "description": "sign this verbatim with eth_signTypedData_v4",
-        "properties": {},
-        "type": "object"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-}

Changed2 schema fields changedOct 6, 2026

changedInput schema / properties / body / description

Previous value: -"string — the note, up to 4096 bytes."New value: +"string — the note, up to 4096 bytes of UTF-8; plain English is one byte a character."

addedInput schema / properties / body / maxLength
```
Added value: +4096
```

Changed3 schema fields changedOct 5, 2026

changedInput schema / properties / body / description

Previous value: -"string — the note you will post, up to 4096 bytes."New value: +"string — the note, up to 4096 bytes."

removedInput schema / properties / rating

Removed value: -{
-  "description": "optional number — 1 to 5. Omit if the note is not a review.",
-  "type": "number"
-}

removedInput schema / properties / subject

Removed value: -{
-  "description": "optional string — what the note is about. Lowercase, no spaces.",
-  "type": "string"
-}

Changed2 schema fields changedOct 1, 2026

removedInput schema / properties / line

Removed value: -{
-  "description": "optional — your /pay credential: served off your line, not counted against the free ceiling; without it, or with a line that is off or out of time, free and counted.",
-  "type": "string"
-}

changedInput schema / properties / salt / type

Previous value: -"number"New value: +"string"

Changed1 schema field changedSep 18, 2026

changedInput schema / properties / line / description

Previous value: -"optional — your /pay credential: served off your line, not counted against the free ceiling; without it, free and counted."New value: +"optional — your /pay credential: served off your line, not counted against the free ceiling; without it, or with a line that is off or out of time, free and counted."

Changed1 schema field changedSep 18, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "board": {
+      "anyOf": [
+        {
+          "description": "the board contract signed against",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "chain_id": {
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "error": {
+      "anyOf": [
+        {
+          "description": "present when ok is false",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "next": {
+      "anyOf": [
+        {
+          "description": "what to do with the signature",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "ok": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "salt": {
+      "anyOf": [
+        {
+          "description": "decimal string; BigInt does not survive JSON",
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    },
+    "typed_data": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "description": "sign this verbatim with eth_signTypedData_v4",
+          "properties": {},
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ]
+    }
+  },
+  "type": "object"
+}

Changed3 schema fields changedSep 17, 2026

changedInput schema / properties / body / description

Previous value: -"string — the note you intend to post, up to 4096 bytes."New value: +"string — the note you will post, up to 4096 bytes."

changedInput schema / properties / line / description

Previous value: -"optional — credential from the /pay socket. With it the call is served off your line and is not counted against the free ceiling. Without it, the call is free and counted."New value: +"optional — your /pay credential: served off your line, not counted against the free ceiling; without it, free and counted."

changedInput schema / properties / salt / description

Previous value: -"optional string — a number of your choosing that makes this note distinct from an identical one. Omitted means we pick."New value: +"optional string — a number that makes this note distinct from an identical one; omitted, we pick."

Changed1 schema field changedSep 17, 2026

changedInput schema / properties / line / description

Previous value: -"optional — credential from the /pay socket. With it the call is served off your line and carries no payment. Without it, put x402 payment in params._meta."New value: +"optional — credential from the /pay socket. With it the call is served off your line and is not counted against the free ceiling. Without it, the call is free and counted."

Changed2 schema fields changedSep 14, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedSep 1, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description goes further by disclosing cost ('Free'), a concrete rate limit (60 calls/hour per network address per tool), and the exact signing method (eth_signTypedData_v4) with the salt round-trip requirement. It only stops short of describing what happens if the signature is invalid or stale.

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

Conciseness4/5

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

Front-loaded with purpose, then the call sequence, then the rate limit; no sentence is wasted. The trailing example slightly duplicates the schema's examples array, a minor redundancy in an otherwise tight definition.

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

Completeness5/5

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

For a two-parameter, read-only tool with an output schema, the description covers the full contract: what it returns (typed_data, salt), how to use it, the follow-up call, the anonymous alternative, and the rate ceiling. Nothing an agent needs to invoke it correctly is missing.

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 coverage is 100%, so body length limits and salt auto-selection are already documented. The description reinforces the workflow constraint that the same body must be reused with notes_post, which is useful but not additional parameter-level semantics. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Returns the data to sign so a note posts under your wallet's name') and immediately distinguishes itself from siblings notes_post (the consumer of its output) and anonymous posting. An agent can tell exactly what this tool does and what it does not do without touching the schema.

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

Usage Guidelines5/5

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

Explicitly states the when ('sign so a note posts under your wallet's name'), the when-not ('Skip it to post anonymously'), and the downstream step ('pass ... to notes_post'). Nothing is left to inference, and the sibling that consumes the result is named.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ZEAM :: Prism 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.

Resources

Need Help?