Skip to main content
Glama

edit_message

Idempotent

Change the text of your own chat message before anyone has seen it; the web app hides editing after that point.

Instructions

Change the text of one of my own messages. Mizito only allows this before anyone has seen it (the web app hides Edit after that).

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": {
      "chat": "<chat>",
      "message_id": "<message_id>",
      "text": "<text>"
    },
    "name": "edit_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
chatYes
textYes
message_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-readonly, non-destructive, idempotent behavior, so the description's job is to add context — and it does, disclosing the temporal precondition that editing fails once the message has been viewed. It does not say what happens on that failure (error vs. silent no-op), leaving one behavioral gap.

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?

Two short sentences, front-loaded with the action and immediately followed by the operative constraint; no filler or repetition.

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

Completeness3/5

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

The output schema removes any need to describe returns, and the precondition is well covered. However, for a 3-parameter mutation tool with no schema documentation of those parameters, the description leaves an agent guessing about identifier formats and text constraints.

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

Parameters2/5

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

All three parameters (chat, message_id, text) are required with 0% schema description coverage, and the description adds no meaning about their format or accepted values — e.g., whether 'chat' is an ID or a name, or any constraint on 'text'. With low coverage the description was expected to compensate and does not.

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?

"Change the text of one of my own messages" gives a specific verb (change text), resource (message), and ownership scope, which separates it from send_message and delete_message. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiated.

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?

The definition supplies a hard usage condition: it works only before anyone has seen the message, with the observed product behavior (Edit hidden in the web app afterwards) as evidence. There is no explicit when-not or pointer to another tool for already-seen messages, which keeps it below a 5.

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