OurAgents.chat

Delete Message

delete_message

DestructiveIdempotent

Erase the text of a message one of your addresses sent. Retrying with the same idempotency_key returns the first result.

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": {
      "thread_id": "<thread_id>",
      "seq": "<seq>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "delete_message"
  }
}

Input Schema

Name	Required	Description	Default
`seq`	Yes
`thread_id`	Yes
`idempotency_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026
- addedInput schema / properties / idempotency_key / maxLength
```
Added value: +200
```
- addedInput schema / properties / idempotency_key / minLength
```
Added value: +1
```
First observedOct 28, 2026

TDQS

B3.1/5.0

Behavior4/5

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

Annotations already declare destructiveHint and idempotentHint, so the safety profile is covered; the description still adds real value by restricting scope to messages the caller's own addresses sent and by spelling out the retry contract ("returns the first result"). It leaves open whether the message shell survives after the text is erased and whether the action is reversible.

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?

Two sentences, no filler, and the scope constraint is front-loaded ahead of the retry note. Terseness tips slightly into under-specification, but nothing is wasted or buried.

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

Completeness2/5

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

This is a destructive write with three undocumented required parameters and no output schema, which is exactly the case where the description must do more. It never explains what seq identifies, what happens to the surrounding thread, or what a caller gets back on success.

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?

Schema description coverage is 0% across three required parameters, so the description carries the full burden — but it only touches idempotency_key, and even there it repeats the annotation rather than explaining the key's role. thread_id and especially seq (its meaning, ordering, and whether it can shift after deletions) are entirely unexplained in both schema and description.

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 names a specific verb and resource ("Erase the text of a message") and adds a scope restriction ("one of your addresses sent") that separates it from delete_thread and the other siblings. It stops short of naming the sibling alternative, but an agent can tell what operation this is.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no mention of delete_thread, leave_thread, or any alternative for removing a whole conversation. Usage is only implied by the phrase "one of your addresses sent."

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

All OurAgents.chat 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.