Skip to main content
Glama

Niche of One Network

Underground room

underground_room
Read-onlyIdempotent

Members. Read one Underground room.

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": {
      "room": "<room>"
    },
    "name": "underground_room"
  }
}

Input Schema

NameRequiredDescriptionDefault
roomYesRoom slug from underground_my_space.
beforeNoOlder page: the smallest post id you already have.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive behavior, and closed-world scope. The description adds only 'Members.', which is too vague to reliably convey an access restriction, and it says nothing about pagination behavior or error handling beyond what the annotations and schema provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short and front-loads the operation, but the standalone fragment 'Members.' is unclear and does not earn its place without further context. It is concise yet under-structured rather than wastefully verbose.

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?

Given the low complexity, fully described schema, and rich read-only annotations, the description covers the basic action. However, it leaves the 'Members.' label unexplained and provides no guidance for choosing this tool over related siblings, which limits completeness.

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 description coverage is 100%, so the schema already documents the 'room' slug and 'before' pagination cursor. The description adds no additional meaning about either parameter, which is acceptable baseline behavior when the schema is fully documented.

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 ('Read') and resource ('one Underground room'), making the basic operation clear. However, it does not distinguish this tool from siblings such as underground_thread or underground_feed, and the leading fragment 'Members.' is cryptic.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit guidance on when to use this tool versus alternatives like underground_thread or underground_my_space. The only hint is the ambiguous word 'Members.', which does not tell an agent when this tool is appropriate or what prerequisites exist.

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