Skip to main content
Glama

Niche of One Network

Comment

underground_comment

Members. Reply to an Underground post. 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": {
      "post": "<post>",
      "body": "<body>"
    },
    "name": "underground_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes
postYesPost id, as the feed shows it.
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.9/5.0
Behavior4/5

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

Annotations only declare write/non-destructive/non-idempotent; the description adds the crucial behavioral detail that this is a gated preview-then-commit operation requiring a server-issued token. That is real disclosure beyond structured fields, though it doesn't cover what the preview displays, duplicate handling, or permission requirements.

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, with the operation named first and the two-phase commit rule immediately after — well front-loaded and free of filler. The orphaned 'Members.' fragment is the only wasted token and costs clarity rather than 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?

No output schema exists, and the description compensates by explaining that the preview returns a preview_token that must be fed back, which is the key return-value contract an agent needs. Missing pieces are secondary: what the preview shows, whether the comment is visible to others before confirmation, and any permission or rate constraints.

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 75% and both confirm and preview_token already have schema descriptions explaining the preview/commit relationship, so the description largely restates the schema. It adds the useful coupling detail that the token must be the one the preview returned, but does nothing for the required post and body parameters.

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 states a specific verb and resource: 'Reply to an Underground post,' which is distinguishable from the sibling post_to_underground that creates a top-level post. The leading fragment 'Members.' is cryptic and doesn't clearly signal whether it means member-only access or a member directory, which slightly muddies the opening.

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 gives explicit invocation guidance for the two-step flow: call once for a preview, then call again with confirm true plus the returned preview_token to commit. It does not name any alternative tool or say when a plain post (post_to_underground) would be preferred over a reply, so it stops short of full when-not guidance.

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