Skip to main content
Glama
Sign In

Moatless

by store.moatless
OverviewDiscussionsAdmin

Send a message

send_message

Sends a message from the signed-in user to the person on Moatless with handle, such as a seller they have a question for, and emails it to them. Only send a message the user has asked you to send, and show them what it says first. Don't use it for anything unsolicited: excessive messaging, such as sending many messages, messaging people who haven't asked to hear from the user, or repeating a message, will get the user's account banned.

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": {
      "input": "<input>",
      "context": "<context>"
    },
    "name": "send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
contextYesExplain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as "the user" or "a buyer".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. Never include personal data, such as names, email addresses or message text; refer to people by role, such as \"the user\" or \"a buyer\".",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "input"
-]New value: +[
+  "input",
+  "context"
+]
  2. Changed1 schema field changed
    • addedInput schema / properties / input / properties / body / maxLength
      Added value: +5000
  3. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only declare openWorldHint and destructiveHint=false; the description adds far more: that the message leaves the platform as an email, that a human confirmation step ('show them what it says first') is required before sending, and that abuse patterns trigger an account ban. These are exactly the side-effect and policy facts an agent needs before invoking an outward-facing write.

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?

Front-loaded with what the tool does, then the confirmation rule, then the prohibition. The anti-spam sentence enumerates examples ('sending many messages, messaging people who haven't asked ... repeating a message') somewhat redundantly, but the ban consequence justifies the length.

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?

For a mutation tool with openWorldHint=true, no output schema, and nested params, the definition covers the risky parts well: outward delivery, confirmation, and policy limits. It does not say what the call returns or what happens if the handle is invalid, which would complete the picture.

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 50% — the nested `context` field is fully documented but `body` and `handle` are not. The description compensates by explaining that `handle` identifies a person on Moatless (e.g. a seller) and that `body` is the message text the user should review first. It says nothing about `context`, though the schema already covers that fully.

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?

States a specific verb and resource ('Sends a message ... to the person on Moatless with `handle`') plus the delivery channel ('emails it to them'), which is unambiguous. It never names a sibling such as reply_to_review or read_messages, so differentiation is left implicit rather than stated.

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?

Gives explicit when-to-use ('Only send a message the user has asked you to send, and show them what it says first') and explicit when-not-to-use ('Don't use it for anything unsolicited: excessive messaging ... or repeating a message'), including the concrete consequence of account banning. An agent has no ambiguity about whether a given request qualifies.

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

All Moatless toolsInspect
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