Prism MCP

notes_sign

notes_sign

Read-onlyIdempotent

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

TableJSON 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

TableJSON Schema

Name	Required	Description	Default
`ok`	No
`next`	No
`salt`	No
`board`	No
`error`	No
`chain_id`	No
`typed_data`	No

Schema Changelog

Changes observed during successful MCP inspections.

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.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, non-destructive), but the description adds non-redundant context: the call is free, rate-limited to 60 calls/hour per network address per tool, and posts under wallet-name attribution if used. It does not explain failure or error behavior, but the disclosure is strong beyond the annotations.

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?

Dense but front-loaded: purpose first, then workflow, then rate limit, then a concrete example. Every sentence carries information, though the run-on workflow sentence could be split for scanability.

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?

With an output schema present, the description needn't spell out return values, and it correctly focuses on workflow, cost, rate limit and the anonymous alternative. An agent has everything needed to call notes_sign and route its output correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the body/salt semantics are already documented; the baseline would be 3. The description adds workflow meaning by tying the body and returned salt to the notes_post call, implying the salt must be reused with the identical body — value beyond the schema.

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 the tool returns signing data so a note posts under your wallet's name, which is a specific purpose distinguishable from notes_post (which submits) and notes_read. The verb is slightly implicit ('The data to sign') rather than a crisp action verb, but the intent is unambiguous.

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?

It gives explicit workflow routing: sign the returned typed_data with eth_signTypedData_v4, then pass the same body, address, signature and salt to notes_post. It also names the alternative path ('Skip it to post anonymously'), so the when-to-use decision is fully specified.

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

All Prism MCP 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?