Skip to main content
Glama

SouthPow crypto & market data

buy_pm_stocks

Paid. Live Polymarket odds for 'stocks' markets, sorted by 24h volume: odds per outcome, volume, liquidity, end date, link. $0.01 USDC on Base. No account, no API key. URL https://southpow.media/v1/polymarket/stocks.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buy_pm_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMarkets, 1-50 (default 10)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the $0.01 USDC payment on Base, that no account or API key is required, and the volume-based sorting. It omits pagination, rate limits, and error behavior, which keeps it just short of 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A dense, front-loaded sentence followed by a short cost/access clause and the URL. Nearly every clause earns its place, though the telegraphic punctuation makes it slightly harder to parse than plain prose.

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 single-optional-parameter tool with no output schema, the description lists the key return fields (odds per outcome, volume, liquidity, end date, link) and the payment model. That is sufficient for correct invocation, with only minor gaps in pagination/error behavior.

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 the single limit parameter is fully documented in the schema (range 1-50, default 10). The description adds no meaning beyond what the schema already provides, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Live Polymarket odds for stocks markets'), plus the sort order (24h volume) and returned fields. An agent can distinguish it from the many topic siblings (buy_pm_bitcoin, buy_pm_election) at a glance.

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 'Paid' prefix and price note indicate there is a cost and no account/API key is needed, which is useful pre-call context. However, it never says when to pick this over the generic buy_polymarket or a topic sibling, so the routing decision is left implicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources