Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Lemmy instance

lemmy_instance_get
Read-onlyIdempotent

Retrieve a Lemmy instance's version, user counts, registration status, and federation settings by providing the instance name. Use it to assess an instance before joining or interacting.

Instructions

Get Lemmy instance version, counts, registration and federation settings. Requires instance.

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

Input Schema

NameRequiredDescriptionDefault
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
includeNoExtra heavy parts to return: `emoji`, `blockedUrls`, `taglines`, comma-separated. Default: none; the site object can be megabytes of custom emoji.
instanceYesRequired. The Lemmy instance, e.g. `lemmy.world`. A URL on the instance is also accepted. Ids and counts belong to this instance.
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.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds value by naming the returned facets (version, counts, registration, federation settings), which matters because there is no output schema. It does not mention the potentially huge optional payloads (emoji, blockedUrls, taglines) even though those are the main behavioral risk.

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, front-loaded sentences with no filler. The 'Requires `instance`' clause is redundant with the required-fields list, a minor waste in an otherwise tight definition.

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 read-only single-resource getter with full schema coverage and no output schema, naming the returned facets gives the agent enough to know what it will get. The main omission is any hint that the instance object can be very large unless `include` is constrained, which the schema covers but the description does not reinforce.

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 the heaviness warning for `include` and the llm_model/conversation_id conventions, is already documented. The description adds only the `instance` requirement, which the schema states as required, 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?

States a specific verb and resource (get a Lemmy instance) and enumerates the payload it returns: version, counts, registration and federation settings. It does not distinguish itself from siblings such as lemmy_instances_list or lemmy_community_get, which an agent must infer from names.

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?

The only guidance is 'Requires `instance`', which is a restatement of a required schema field rather than a when-to-use rule. There is no mention of when to prefer this over lemmy_instances_list or other *_get siblings, leaving the agent to infer the choice.

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