Skip to main content
Glama

Niche of One Network

Underground notifications

underground_notifications
Read-onlyIdempotent

Members. Your replies, mentions and messages notifications.

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

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description contributes only the notification categories (replies, mentions, messages) surfaced to the caller — modest return-content context. It says nothing about ordering, authentication, unread state, or how the `before` cursor behaves, so with the lower bar set by annotations this lands at a 3.

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

Conciseness2/5

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

Two sentence fragments, one of which ("Members.") carries no discernible meaning and is not front-loaded with an action verb. It is short, but brevity here comes from under-specification rather than disciplined editing. An agent reading top-down learns the resource only after parsing a stray fragment.

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

Completeness2/5

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

For a notifications retrieval tool the description omits what an agent most needs: that results are a paginated, newest-first list and that `before` is the cursor for older pages. There is no output schema, so the description is the only place ordering and page-walking behavior could be stated, and it is silent on both. Annotations cover only the safety profile.

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?

The single `before` parameter is fully documented in the schema ("Older page: the smallest post id you already have"), giving 100% schema description coverage. The description adds no meaning beyond that, but per the baseline rule, high coverage with no compensating detail in prose still merits a 3.

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 phrase "Your replies, mentions and messages notifications" does identify the resource and the notification categories covered, which goes slightly beyond the title. However, there is no verb at all (list? fetch? mark read?) and the leading fragment "Members." is unexplained, so the operation stays vague. It also does nothing to separate itself from the sibling underground_messages, which an agent could easily confuse with message notifications.

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 when-to-use statement, no prerequisite, and no named alternative. The presence of underground_messages and underground_feed among siblings makes the missing guidance costly, since an agent has to guess whether this tool or a message-listing tool is the right call. Usage is only inferable from the word "notifications."

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