Skip to main content
Glama

Niche of One Network

Send a message

underground_send_message

Members. Send a direct message to a member, where the site allows it. Shows a preview first; call again with confirm true and the preview_token it returned to commit.

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": {
      "handle": "<handle>",
      "body": "<body>"
    },
    "name": "underground_send_message"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
handleYesMember handle, without the @.
confirmNoLeave out for a preview. true commits, with the preview_token.
preview_tokenNoThe preview_token the preview returned. Needed with confirm true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=false, destructiveHint=false and idempotentHint=false; the description goes further by explaining why non-idempotent behavior exists (the second call with confirm commits the send) and that the action is gated by site policy. It does not mention rate limits or error modes, but the mutation contract itself is well disclosed.

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?

Three short sentences, front-loaded with the action and then the protocol; no filler. The standalone "Members." fragment is the only awkward element, reading as a leftover taxonomy label rather than content.

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 no output schema, the description still tells the agent that the preview returns a preview_token, which is the one return value the agent must handle. For a four-parameter, two-phase messaging tool that is close to complete; only error/permission failure behavior is left unstated.

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

Parameters5/5

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

Beyond the schema's 75% coverage, the description explains the causal relationship between confirm and preview_token: the token comes from the preview response and must accompany confirm true. That sequencing is not derivable from the schema, which merely labels each field in isolation.

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 gives a specific verb and resource ("Send a direct message to a member") plus a capability caveat ("where the site allows it"), which is enough to distinguish it from read-oriented siblings like underground_messages. The leading fragment "Members." is a terse category tag rather than a sentence and adds little, and no sibling is named to sharpen the boundary.

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?

It clearly states the required two-step invocation: preview first, then repeat the call with confirm true and the returned preview_token. That is concrete when/how guidance an agent could otherwise get wrong. It stops short of naming an alternative tool (e.g. a public post or comment) or stating when not to DM someone.

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