Skip to main content
Glama

Prediction market sentiment

prediction_market_sentiment
Read-only

Aggregate sentiment across all prediction markets related to a topic. Searches Polymarket, analyzes probabilities, and returns a 0-100 sentiment score with bullish/bearish label. Costs $0.01 USDC per call.

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": {
      "topic": "<topic>"
    },
    "name": "prediction_market_sentiment"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax related markets to analyze
topicYesTopic to analyze (e.g. 'Solana', 'Fed policy', 'Bitcoin', 'AI regulation')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful behavior beyond that: the underlying data source (Polymarket), the output shape (0-100 score with bullish/bearish label), and the cost per call ($0.01 USDC). It omits latency, rate limits, or failure modes, but the core behavioral profile is present.

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 sentences, front-loaded with the action and scope, followed by output shape and cost. No filler or redundancy.

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?

With no output schema, the description carries the return-value burden and does so adequately (score + label). It also discloses cost and data source, which matter for a paid, read-only, open-world tool. It could say more about what 'aggregate' returns (e.g., underlying markets or confidence), but nothing critical is missing for a correct invocation.

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%; the topic parameter has examples and limit has a default and explanation. The description adds nothing about parameter meaning or format beyond the schema, which is the expected baseline when schema coverage is complete.

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?

States a specific verb and resource: 'Aggregate sentiment across all prediction markets related to a topic', names the source (Polymarket), and describes the output (0-100 score with bullish/bearish label). It does not distinguish itself from siblings like crypto_sentiment, fear_greed_index, or prediction_market_aggregator, leaving an agent to infer the boundary.

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 guidance on when to choose this over the numerous sibling tools (crypto_sentiment, prediction_market_odds, prediction_market_aggregator, polymarket_quote). The only decision-relevant context is the $0.01 cost, which is useful but not usage routing.

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