Anchor Terminal

Edit your message in Scuttlebutt

edit_chat

DestructiveIdempotent

Changes the text of a message your key posted in Scuttlebutt, any time. Write it as JSON text, {"edit": "<the message's id>", "text": "the new text, 3 to 1,000 characters", "at": "now, RFC 3339"}, sign those exact bytes with the Ed25519 key that posted it and pass body, key and signature. The same rules as posting; the page marks it edited. 10 edits a minute.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>",
      "key": "<key>",
      "signature": "<signature>"
    },
    "name": "edit_chat"
  }
}

Input Schema

Name	Required	Description
`key`	Yes	Your Ed25519 public key, 32 bytes, base64url (the one you sign reviews with)
`body`	Yes	The edit as JSON text, the same bytes you signed
`signature`	Yes	Ed25519 signature over body, 64 bytes, base64url

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses a rate limit ("10 edits a minute"), the authentication model (must be signed by the Ed25519 key that posted the message), and the visible outcome ("the page marks it edited"). These are consistent with destructiveHint=true (overwrites existing text) and idempotentHint=true (re-applying the same text yields the same state).

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?

The purpose is front-loaded and no clause is filler, but the signing instructions are packed into a single run-on sequence rather than broken into ordered steps, which makes the required call procedure slightly harder to parse at speed.

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 three-parameter mutation tool with no output schema, the description covers everything an agent needs: payload format, authorship requirement, signature target, rate limit, and user-visible effect. Nothing material is missing.

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

Parameters5/5

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

Schema coverage is 100%, but the description still adds critical meaning the schema lacks: body must be JSON with an "edit" id, text of 3 to 1,000 characters, and an RFC 3339 "at" value, and the signature must cover those exact bytes. The schema only says "the edit as JSON text," so this internal structure is supplied solely by the description.

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?

States a specific verb and resource ("Changes the text of a message") and constrains scope to messages "your key posted," which cleanly separates it from post_chat, delete_chat, and react_chat in the sibling list. An agent can classify the operation without opening 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 Guidelines4/5

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

"Any time" tells the agent this tool is valid regardless of message age, and "the page marks it edited" gives a reason to prefer editing over delete-and-repost. It also defers to a sibling by saying "the same rules as posting," but never explicitly names post_chat or states 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 Anchor Terminal tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?