Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Stack Overflow post citation

stack_overflow_post_citation_get
Read-onlyIdempotent

Generate BibTeX, AMS, and text citations for a Stack Overflow question or answer from its post ID, so you can cite technical discussions correctly.

Instructions

Get a BibTeX, AMS and text citation for a Stack Overflow question or answer. Requires postId.

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

Input Schema

NameRequiredDescriptionDefault
siteNoStack Exchange site, by its API name (`askubuntu`, `serverfault`, `math`, `ru.stackoverflow`). Default: `stackoverflow`. The sites endpoint lists them all.
postIdYesRequired. Post id (a question or an answer) on the chosen site, e.g. `11227902`.
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.8/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 safety is covered. The description adds genuine value by naming the returned citation formats, but says nothing about rate limits, auth needs, or that three parameters are mandatory on every call.

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?

Two short sentences with zero padding; the capability and output formats are front-loaded and the requirement follows. Nothing could be trimmed without losing information.

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 citation formatter with no output schema, naming the three citation formats is the essential missing piece and it is present. The gap is that the definition never signals the other two required parameters (context, llm_model) or the conversation_id echoing protocol, which an agent would only discover in the schema.

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 all five parameters (site, postId, context, llm_model, conversation_id) are fully documented in the schema itself. The description only restates that postId is required, adding no new semantic detail beyond what the schema provides, making 3 the correct baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Get) and resource (citation for a Stack Overflow question or answer) plus the exact output formats — BibTeX, AMS, text. No sibling tool produces citations, so the agent can distinguish it immediately from post_get or question_get style tools.

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 description notes it 'Requires `postId`' but gives no explicit when-to-use vs. when-not guidance and no mention of the two other required parameters (context, llm_model) or the conversation_id flow. An agent can infer this is the citation tool, but must open the schema to learn the invocation requirements.

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