Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Ask in natural language

nl_ask_post
Read-onlyIdempotent

Routes a natural-language social-data question to the correct public API lookup when the operation is unknown, so you can identify the right typed tool before continuing.

Instructions

Route a natural-language social-data question to the right lookup when you do not yet know the typed tool — prefer typed tools once the operation is known. Accepts a natural-language query.

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

Input Schema

NameRequiredDescriptionDefault
queryYesNatural-language question to route to a public API lookup.
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=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so the safety and side-effect profile is covered structurally. The description adds the routing behavior, but omits two notable traits that only appear in the schema: the server-issued conversation_id handshake and the prohibition on parallel calls before receiving it. For an open-world dispatch tool, those are the behaviors an agent most needs surfaced.

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?

The routing guidance is front-loaded and the whole definition is two sentences. The trailing 'Accepts a natural-language query' largely repeats what the first sentence already established, so one clause could be cut without losing information.

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

Completeness3/5

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

There is no output schema, so the description should convey what comes back from a routing call — a suggested lookup, a result set, or a conversation identifier — and it does not. The parameters are fully documented in the schema, but the return contract for this router remains an open question for the calling agent.

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%, including detailed guidance for context, llm_model and conversation_id, so the schema does the heavy lifting. The description only restates that the query is natural language, adding no meaning beyond what the parameter descriptions already provide; baseline 3 is appropriate.

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 uses a specific verb and resource ('Route a natural-language social-data question to the right lookup') and explicitly separates itself from typed tools. What is less clear is whether the tool merely routes or also executes the lookup and returns data; the word 'Route' implies dispatch, but the outcome is not stated.

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 states the trigger condition ('when you do not yet know the typed tool') and the exclusion ('prefer typed tools once the operation is known'), which is genuine when/when-not guidance. It stops short of saying what to do with ambiguous or multi-part questions, and no specific alternative tool is named.

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