Skip to main content
Glama

Niche of One Network

Underground feed

underground_feed
Idempotent

Members. Read the Underground wall as you see it on the site (all rooms you can read, or only people you follow). Like the site, it moves your last-visit marker.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "underground_feed"
  }
}

Input Schema

NameRequiredDescriptionDefault
beforeNoOlder page: the smallest post id you already have.
followingNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The description does real work here: it discloses that the call moves the last-visit marker, which explains why annotations declare readOnlyHint=false despite this being a read. That reconciles an otherwise puzzling annotation. However, it says nothing about auth requirements implied by 'Members.', throttling, or what the response contains.

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 plus a leading fragment. The scope statement and the side-effect warning are front-loaded with no filler, though the bare 'Members.' token is unclear and slightly undermines the structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the agent learns nothing about the returned shape (post list, ordering, cursor behavior) beyond the 'before' parameter hint. The side-effect disclosure is valuable, but return expectations and the membership gate remain underspecified for a feed tool.

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 50%: 'before' is documented in the schema as the smallest post id already held, and the description's 'only people you follow' clause supplies the meaning of the undocumented 'following' boolean. That partially compensates, but it adds no pagination syntax or default behavior beyond the schema.

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 ('Read the Underground wall') plus the two scope modes ('all rooms you can read, or only people you follow'). It is clearly distinguishable from write-oriented siblings like post_to_underground or underground_comment, though the opening fragment 'Members.' is an ambiguous dangling label.

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 parenthetical implies when to use the narrow scope (people you follow) vs the broad one, but it never states prerequisites for calling it or points to any alternative sibling for a different view. Usage is inferable from the scope note rather than explicitly guided.

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