Skip to main content
Glama

Niche of One Network

Underground thread

underground_thread
Idempotent

Members. Read one thread with its replies. Like the site, it marks that thread's notifications read.

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>"
    },
    "name": "underground_thread"
  }
}

Input Schema

NameRequiredDescriptionDefault
postYesPost id, as the feed shows it.

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?

The description discloses the key non-obvious trait: the call has a write side effect, marking that thread's notifications read, which explains why readOnlyHint is false on an otherwise read-shaped tool. It also frames the behavior as matching the site, though it does not say how the reply list is ordered or capped.

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 short sentences with the core action front-loaded and no filler. The dangling "Members." opener is unexplained and slightly muddies the lead.

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 single-parameter read tool with no output schema, the description covers what is retrieved (thread plus replies) and the notification side effect. Ordering, reply pagination, and error behavior for an unknown id remain unstated but are minor at this complexity.

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?

Only one parameter, and the schema documents it fully ("Post id, as the feed shows it") at 100% coverage. The description adds no syntax, format, or edge-case detail beyond the schema, so the baseline 3 applies.

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?

"Read one thread with its replies" is a specific verb+resource+scope, and it clearly contrasts with feed/comment siblings. The leading fragment "Members." is opaque but the operational sentence is unambiguous.

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?

Usage is implied through the resource: fetch a single thread by post id. There is no explicit statement of when to prefer this over the feed or commenting tools, and no prerequisites or exclusions are named.

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