Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Whoami

auth_whoami
Read-onlyIdempotent

Retrieves the authenticated API account tied to the current session so you can verify identity and account context before making social data requests.

Instructions

Get the authenticated API account for this session.

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

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description adds the useful behavioral nuance that the result reflects the API account behind the current session rather than an arbitrary user. It says nothing about caching, latency, or what the response actually contains, and with no output schema that is a real gap.

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 with no waste. It is arguably too terse for a tool whose entire value is the returned account object, but nothing is redundant or buried.

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?

The operation is simple and its safety profile is carried by annotations, so not much is required. However, no output schema exists and the description never indicates what account fields come back, and it does not acknowledge the required session/meta parameters - minor but real omissions for a tool an agent will typically call first.

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 coverage is 100%, and all three parameters - including the unusual context, llm_model, and conversation_id - are fully documented in the schema. The description adds no parameter detail, which is acceptable given the baseline, but it also gives no hint that the tool requires these meta-parameters at all.

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 states a specific verb and resource: get the authenticated API account. It also clarifies the identity is credential/session-scoped, which distinguishes it from the content-fetch siblings. It does not explicitly name an alternative or state that it is the only identity-inspection tool, but the purpose is unambiguous.

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?

"for this session" is the only contextual hint; there is no statement of when an agent should call this (e.g., to verify which account/tenant the credentials belong to, or to confirm permissions before a mutation). No exclusions or alternatives are given, and none are inferable from the sentence alone.

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