Skip to main content
Glama

Niche of One Network

Follow

underground_follow
Idempotent

Members. Follow or unfollow a member. Shows a preview first; call again with confirm true and the preview_token it returned to commit.

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": {
      "handle": "<handle>",
      "on": "<on>"
    },
    "name": "underground_follow"
  }
}

Input Schema

NameRequiredDescriptionDefault
onYes
handleYesMember handle, without the @.
confirmNoLeave out for a preview. true commits, with the preview_token.
preview_tokenNoThe preview_token the preview returned. Needed with confirm true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the annotations (non-read-only, idempotent, non-destructive), the description discloses the non-obvious preview-then-commit protocol with a token round-trip, which the annotations do not convey. It doesn't say what the preview contains, but the core behavioral model is clear and consistent with destructiveHint=false.

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

Conciseness5/5

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

Three short sentences, front-loaded with purpose followed by the operational rule. No wasted wording or repetition of schema content.

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 4-parameter mutation with no output schema, the description covers purpose, the required workflow, and the token handoff. It omits how to predict confirm's effect on `on` (follow vs unfollow semantics per value), a minor gap, but overall complete enough to call correctly.

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 75% and already documents confirm and preview_token, but the description adds the causal link -- the token must be the one the preview returned -- that clarifies sequencing between the two optional parameters. That meaning goes beyond the individual field text.

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 pair ('Follow or unfollow') and resource ('a member'), which is clearly distinct from sibling write tools like post_to_underground or underground_react. The leading 'Members.' label is a mild structural quirk but does not obscure the purpose.

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

Usage Guidelines4/5

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

It gives a concrete two-step usage rule: call once for a preview, then call again with confirm true and the returned preview_token to commit. It does not name exclusions or alternatives, but the preview/commit workflow is the key guidance an agent needs here.

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