Skip to main content
Glama
Octav API MCP Server

Octav API MCP Server

Official
by Octav-Labs

Get Polymarket Positions

octav_get_polymarket
Read-only

Retrieve Polymarket prediction market positions and collateral for a Polymarket proxy wallet address. Use the proxy wallet shown on the Polymarket profile; regular wallet proxies are not resolved.

Instructions

Get the Polymarket prediction market positions and collateral of a Polymarket (proxy) wallet. Pass the proxy wallet itself, as shown on the Polymarket profile; a regular wallet's proxy is not looked up. Costs 1 credit.

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

Input Schema

NameRequiredDescriptionDefault
addressYesPolymarket (proxy) wallet address (0x...), as shown on the Polymarket profile

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / address / description
      Previous value: -"Ethereum wallet address (0x...)"New value: +"Polymarket (proxy) wallet address (0x...), as shown on the Polymarket profile"
  2. First observedv1.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive and open-world behavior, so the bar is lower; the description still adds non-obvious context by disclosing the 1-credit cost and the proxy-wallet-only constraint. It does not describe response shape, empty-position handling, or pagination, which keeps it below a 5.

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?

Three short sentences, front-loaded with the purpose, then the critical parameter constraint, then the cost. No redundant or filler wording.

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 simple one-parameter read tool with annotations covering the safety profile, the description supplies scope, the proxy-wallet requirement, and credit cost. The only gap is what the response looks like (there is no output schema), which is partially mitigated by naming 'positions and collateral'.

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?

With a single required parameter at 100% schema description coverage, the schema already fully documents the address field. The description reinforces the proxy-wallet requirement but adds little syntactical or semantic detail beyond what the schema states, so the baseline 3 applies.

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 ('Get') and a tightly scoped resource ('Polymarket prediction market positions and collateral'), which is clearly narrower than the generic portfolio/Nav siblings. It doesn't explicitly contrast itself with a sibling such as octav_get_portfolio, but the venue-specific scope makes it distinguishable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives the key usage condition: pass the Polymarket proxy wallet as shown on the profile, and notes that a regular wallet's proxy is not looked up. That effectively tells the agent when this tool is invalid, though it stops short of naming alternative tools for non-Polymarket holdings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.