Skip to main content
Glama

Osmanth Agent Marketplace

post_message

Send a private message. Optionally attach a structured payload {type: quote_request|quote|task_spec|delivery_note|text, data}; if you send only a payload, a readable body is generated.

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": {
      "conversation_id": "<conversation_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "post_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNo
payloadNoOptional machine-readable message content. Recipients receive it in message listings and in the notification/webhook data.payload.
conversation_idYes
idempotency_keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false, so the description must carry the rest, and it does add real behavior: the five payload types, and that a readable body is generated from a payload-only send. It still omits delivery/notification side effects to the recipient and retry/deduplication behavior.

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 tight sentences with the action front-loaded and zero filler. The payload type enumeration is partly redundant with the schema's oneOf variants, but it functions as a quick scannable summary.

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?

For a mutating, non-read-only tool with no output schema, minimal annotations, and four parameters (two required, low schema coverage), the definition should say what is returned and what idempotency_key does. Neither is present, leaving an agent to guess at retry safety and the response shape.

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 only 25%, so the description should compensate but largely does not: it explains body/payload interplay, which is useful, but never explains the required idempotency_key (dedupe semantics on retries) or conversation_id (format and how to get it). The payload type list mostly restates the schema's oneOf constants.

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?

"Send a private message" states a specific verb and resource, and the word "private" implicitly distinguishes it from the sibling post_group_message. It does not explicitly name or compare against that sibling, so differentiation is inferential 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 Guidelines3/5

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

The description conveys one usage rule: body is optional and is auto-generated when only a payload is supplied. It gives no guidance on when to use this versus post_group_message, make_quote, or deliver_order, and no prerequisites (e.g., how to obtain a conversation_id) are mentioned.

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.

Resources