Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Polymarket user

polymarket_user_get
Read-onlyIdempotent

Fetches a Polymarket user's public profile and headline statistics by wallet address or username, so you can verify identity and review trading performance data.

Instructions

Get a Polymarket user's public profile and headline statistics by wallet or username. Requires walletOrUsername.

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

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.
walletOrUsernameYesRequired. Wallet address (0x and 40 hex digits) or username. A username costs one more lookup to find the wallet.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety and idempotency are covered. The description adds only that the profile is public and returns 'headline statistics', without saying what those statistics are or whether results are cached. It is a modest addition over the annotations, not a rich behavioral disclosure.

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 compact sentences, with the operation and its scope stated first and the required identifier second. No padding or redundant framing.

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?

With four parameters, an output schema absent, and full schema coverage, the description is adequate but thin. It never explains what 'headline statistics' means as a return shape, which matters because there is no output schema. It also omits the analytics and conversation_id plumbing parameters, though those are self-documented.

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 baseline is 3. The description confirms the wallet-or-username duality, but the schema already explains both formats and the extra lookup cost of a username. The description adds no meaning beyond the structured fields.

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 gives a specific verb and resource: 'Get a Polymarket user's public profile and headline statistics'. It also states the accepted identifier forms. It stops short of distinguishing the tool from close siblings such as polymarket_user_stats_get, since 'headline statistics' overlaps with a dedicated stats tool.

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?

There is no when-to-use guidance and no routing to alternatives. 'Requires wallexOrUsername' restates a schema constraint rather than advising usage. An agent gets no signal about when to pick this over polymarket_user_stats_get, user_activity_list, user_pnl_list, or user_positions_list.

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