Skip to main content
Glama
Sign In
mcp-server-polymarket

mcp-server-polymarket

by tukorama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get a public Perps account

get_perps_public_account
Read-onlyIdempotent

Check whether an address has a Perps account and retrieve its public equity and open positions, optionally including builder profile details.

Instructions

Whether an address has a Perps account, and its public equity and open positions.

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": {
      "address": "<address>"
    },
    "name": "get_perps_public_account"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesOwner address.
include_builderNoAlso the builder profile.

Output Schema

NameRequiredDescriptionDefault
errorsNo
addressYes
builderNo
portfolioNo
registeredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds that results are 'public' and include equity and open positions, but says nothing about behavior for non-existent accounts (null vs empty vs error) or how fresh the data is, leaving a modest gap for an openWorld read.

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?

A single front-loaded sentence with no filler; the core question (does the account exist, what does it hold) leads. Nothing in it could be removed 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?

The tool is a simple two-parameter read with a full output schema, so the description does not need to enumerate return fields. It covers the essential scope and the public nature of the data; only edge-case behavior for missing accounts is unstated.

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%, with the address pattern and the include_builder default fully documented in the schema. The description adds no meaning beyond that, which is the expected baseline when the schema carries parameter semantics.

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 the resource (a Perps account identified by address) and the payload (existence, public equity, open positions), which is specific enough to distinguish it from market-data siblings like get_perps_book or get_perps_tickers. It stops short of explicitly contrasting it with account-oriented siblings such as get_profile or get_user_overview.

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?

The phrasing 'Whether an address has a Perps account' implies a lookup-or-verify use case, but there is no explicit when-to-use or when-not-to-use guidance, and no named alternative for related account queries. Usage is inferable but not directed.

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