Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Mastodon server peers

mastodon_server_peers_list
Read-onlyIdempotent

List the domains a Mastodon server federates with by providing its host; use the returned cursor to page through results.

Instructions

List the domains a Mastodon server federates with. Requires host. Returns a list (use cursor when paginated).

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": {
      "host": "<host>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "mastodon_server_peers_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoOnly domains containing this text.
hostYesRequired. The Mastodon server to ask, e.g. `mastodon.social`. A server URL is also accepted. The server you name is the one that answers.
limitNoItems per page, 1 to 1000. Default: 100.
cursorNoPass `page.nextCursor` from the previous response to get the next page.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds two genuinely useful behavioral facts beyond that: the call returns a list and pagination is handled via cursor. It does not describe the shape of returned domain entries or any rate/scale limits for a potentially large federation list.

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 with zero padding, and the core purpose is front-loaded before the prerequisite and pagination notes. Every clause carries information an agent can act on.

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 simple, read-only list tool with full schema coverage, four annotations, and no output schema, the description covers purpose, the key required input, and pagination well enough to call correctly. The only shortfall is a lack of guidance on the optional domain filter and expected result volume, which are minor for this complexity.

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 every parameter is already documented in the schema, including `host`, `q`, `limit`, and `cursor`. The description only repeats the `host` requirement and the cursor-for-pagination idea without adding format, defaults, or filtering semantics, so baseline 3 applies.

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 names a specific verb and resource — 'List the domains a Mastodon server federates with' — which is concrete and distinguishable from sibling reads like mastodon_server_get or mastodon_server_blocks_list. It does not explicitly name or contrast a sibling, which keeps it from a 5.

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 only implied: the phrase 'federates with' signals this is the peers/federation view rather than blocks or activity, and 'Requires `host`' states a prerequisite. There is no explicit when-to-use vs when-not guidance and no mention of the `q` filtering option as a reason to prefer this over other server listing tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools