Skip to main content
Glama

Niche of One Network

Underground messages

underground_messages
Idempotent

Members. Your direct-message conversations, or one conversation by handle (opening it marks it read, as on the site).

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_messages"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoMember handle, without the @.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

The annotations declare readOnlyHint=false and idempotentHint=true without explaining why a 'list' is not read-only; the description resolves that by disclosing 'opening it marks it read, as on the site.' That is genuine behavioral context beyond the structured fields, though it still says nothing about pagination, ordering, or result contents.

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 carry the scope, both modes, and the side effect with no filler. The leading category label 'Members.' is the only soft spot — it conveys grouping rather than behavior — but it is brief enough not to distract.

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 description carries some burden for describing what comes back, and it does not indicate whether conversations include last message, unread counts, or pagination. For a simple single-parameter read tool the core is covered, but the return shape is left entirely to inference.

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

Parameters4/5

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

Schema coverage is 100% and the schema already defines the handle format, so the baseline is 3. The description goes beyond that by explaining what the handle semantically selects (a single conversation rather than the full list) and by attaching the read-marking side effect to that parameter path.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource precisely — 'your direct-message conversations, or one conversation by handle' — and distinguishes the two modes it operates in. However, it never states the verb (list/read) and does not differentiate itself from nearby siblings such as underground_send_message or underground_thread, so the purpose is inferable rather than explicit.

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 argument shape: omit the handle to get all conversations, supply a handle to open one. That is a real routing rule an agent can act on, but there is no explicit when-to-use framing and no comparison to alternative tools for reading member conversations.

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