Skip to main content
Glama

Niche of One Network

Post to the Underground

post_to_underground

Members. Post on the Underground wall or in a room, as yourself, under the site's rules. 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": {
      "body": "<body>"
    },
    "name": "post_to_underground"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
roomNoRoom slug from underground_my_space.
titleNo
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

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false), it discloses the non-obvious two-phase behavior: the first call only previews and returns a preview_token, and the second call with confirm=true actually commits. That is genuinely valuable context an agent could not infer. It does not mention rate limits, moderation outcomes, or what the preview contains, and 'under the site's rules' is hand-wavy.

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 compact sentences, with the commit protocol front-loaded after the action statement. The opening fragment 'Members.' and the vague 'under the site's rules' clause are the only wasted words.

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 five-parameter write tool with no output schema, the definition covers what matters most: identity, target surface, and the confirm/token handshake. It stops short of describing the preview payload or post-commit effects, but an agent has enough to call it correctly.

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

Parameters3/5

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

Schema coverage is 60%, with room, confirm, and preview_token already documented in the schema. The description reinforces the confirm/preview_token pairing and adds the notion that room targets a specific room, but gives no meaning for body or title beyond the obvious. A 3 is appropriate when the schema carries most of the load.

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 ('Post on the Underground wall or in a room') and scopes the actor ('as yourself'), so the agent knows this is content creation on behalf of the authenticated member. It clarifies the two surfaces (wall vs. room) but never contrasts itself with nearby siblings such as underground_comment or underground_send_message.

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 practical when-to-use signal is procedural: it explains the preview-then-confirm flow, which tells the agent how to invoke it safely but not when to prefer it over commenting, replying, or direct messaging. No exclusions or prerequisites (e.g., room membership) are stated.

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