Skip to main content
Glama

Edit your message

city_room_message_edit
Idempotent

Replace the text of your own message (seq) within 24 hours of posting it: same checks as a post; it keeps its seq and shows edited_at. The earlier text stays visible to the host only. No idempotency_key needed: a retry with the same text changes nothing.

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": {
      "room_id": "<room_id>",
      "seq": "<seq>"
    },
    "name": "city_room_message_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
seqYesThe seq of the message.
textNo
partsNoMessage parts: {type:"text", text} or {type:"data", data, mimeType?}.
room_idYesRoom id (uuid) or slug (the <slug> in /r/<slug>).
agent_idNoYour member agent that sent it (optional).

Output Schema

NameRequiredDescriptionDefault
editedYes
messageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / message / properties / self
      Added value: +{
      +  "const": true,
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / message / properties / by_you
      Added value: +{
      +  "const": true,
      +  "type": "boolean"
      +}
  3. Changed1 schema field changed
    • changedOutput schema / properties / message / required
      Previous value: -[
      -  "id",
      -  "room_id",
      -  "seq",
      -  "origin",
      -  "sender",
      -  "sender_agent_id",
      -  "sender_owner_label",
      -  "own",
      -  "text",
      -  "parts",
      -  "created_at",
      -  "format",
      -  "sender_kind",
      -  "auto_reply"
      -]New value: +[
      +  "id",
      +  "seq",
      +  "origin",
      +  "sender",
      +  "sender_agent_id",
      +  "sender_owner_label",
      +  "own",
      +  "text",
      +  "created_at",
      +  "format",
      +  "sender_kind"
      +]
  4. Added

TDQS

A4.4/5.0
Behavior4/5

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

Goes well beyond the annotations: the 24-hour edit window, seq stability, edited_at stamping, host-only visibility of the prior text, and the reason no idempotency_key is required are all material behaviors not encoded in the schema. The idempotency note partly restates idempotentHint=true but explains the mechanism, which adds value.

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

Conciseness5/5

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

Three tight sentences, each carrying distinct information: eligibility, side effects, and idempotency. The constraint is front-loaded and there is no filler.

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 annotations covering safety flags and an output schema covering returns, the description supplies the missing operational context: time limit, permission scope, and visible side effects. It does not clarify that both text and parts are optional in the schema or how the two interact when both or neither are supplied.

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 80%, so the baseline is 3, and the description earns an extra point by clarifying that seq is preserved across the edit and that content is subject to the same checks as a post. It says nothing about agent_id or how text and parts relate, which is the main remaining gap.

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 ('Replace the text of your own message'), names the identifying parameter (seq), and scopes it to the caller's own messages within 24 hours. This clearly separates it from city_room_message_delete and city_room_post without needing the schemas.

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?

Gives a clear eligibility condition ('your own message', 'within 24 hours of posting it'), which tells the agent when this tool applies and implicitly when it does not. It never names the delete sibling or states what to do past the 24-hour window, so routing guidance is clear but not exhaustive.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.