Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Polymarket users

polymarket_users_search
Read-onlyIdempotent

Search Polymarket users by name or partial username to retrieve matching wallet addresses and identify accounts for further analysis.

Instructions

Search Polymarket users by name and get their wallet addresses. Requires query. Returns a list.

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": "polymarket_users_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoItems per page, 1–50. Default: 10.
queryYesRequired. A username or part of one.
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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. Beyond that the description adds only 'Returns a list', saying nothing about pagination via `limit`, empty-result behavior, or the odd requirement to obtain conversation_id before issuing parallel calls (that lives only in the schema).

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?

Three short sentences, front-loaded with the core action and result, with no filler or hedging. 'Returns a list' is thin but costs almost nothing and does set an expectation about the response shape.

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?

This is a simple search tool and the description covers the essential action, but with no output schema the agent gets no detail on what the returned user objects contain beyond wallet addresses, and nothing indicates how to page through results using `limit`. Adequate but with clear gaps for an agent deciding how to consume the output.

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 the baseline is 3; every parameter including `limit` bounds and the analytics/context fields is documented in the schema itself. The description's 'Requires `query`' merely repeats what the schema already marks required, adding no new meaning.

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 names a specific verb and resource (search Polymarket users by name) and states the value returned (wallet addresses), which is more than a restatement of the name. It does not distinguish this from the sibling polymarket_search, so an agent must infer that one searches users and the other searches markets/events.

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 or when-not-to-use guidance and no named alternative, even though polymarket_search exists as a plausible confusable sibling. The only implicit signal is that a username is the search key, which the required `query` parameter already conveys.

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