Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Mastodon server

mastodon_server_get
Read-onlyIdempotent

Retrieve a Mastodon server's public profile, rules, and statistics by host to evaluate or understand an instance before interacting with it.

Instructions

Get a Mastodon server's public profile, rules and statistics. Requires host.

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

Input Schema

NameRequiredDescriptionDefault
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.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNoComma-separated extras: `rules` (the server's rules) and `about` (its long description).
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

B3.4/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 the content scope (profile, rules, statistics), but omits the notable nuance that rules/about are only fetched when the optional `include` array asks for them, and says nothing about the conversation_id handshake or pagination-free single-object return.

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?

A single front-loaded sentence naming the verb and resource. The trailing 'Requires `host`' is largely redundant with the schema's required list, which is the only wasted clause.

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

Completeness5/5

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

With 100% schema coverage, rich annotations, and a simple single-object read, the description supplies enough to select and call the tool correctly. The remaining detail (include semantics, conversation_id flow) lives fully in the schema, so nothing essential is missing.

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 including `include` and `conversation_id` is documented in the schema; baseline 3 applies. The description contributes only the `host` requirement, which the schema already states as required, and adds no meaning about `include` gating.

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?

States a specific verb ('Get') and resource ('a Mastodon server's public profile'), plus the payload returned (rules and statistics). The 'server' framing distinguishes it from the profile-level siblings such as mastodon_profile_get, though the description never names an alternative to confirm that contrast.

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?

'Requires `host`' restates a required field rather than telling the agent when to choose this tool over mastodon_profile_get or mastodon_server_activity_list. No when-to-use or when-not-to-use condition is given.

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