Skip to main content
Glama

Polymarket MCP by Nova (CIVAI)

get_market_news_context

Returns recent news articles relevant to a Polymarket market topic, useful for grounding LLM analysis.

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

Input Schema

NameRequiredDescriptionDefault
slugNoMarket slug to derive topic from
limitNoMax articles (default 10, max 30)
queryNoOptional explicit keyword(s) to search
notification_messageNoShort user-facing sentence for this action if the follow-up reply fails. Plain text only; do not mention template syntax or variable names.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added
  12. Removed
  13. Added
  14. Removed
  15. Added
  16. Removed
  17. Added
  18. Removed
  19. Added
  20. Removed
  21. First observed

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose the news source, freshness/lookback window, caching or rate limits, or what happens when neither slug nor query is supplied (all params are optional), nor what an article object contains.

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 single front-loaded sentence with no filler; the verb and resource come first. It is efficient, though its brevity edges toward under-specification rather than tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should explain the return shape (article fields, number of items) and default behavior when no slug or query is passed. For a 4-parameter tool with all-optional inputs, one sentence leaves an agent guessing what a call with an empty argument set actually does.

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%, so slug, limit (default 10, max 30), query, and notification_message are already documented in the schema — baseline 3 applies. The description adds nothing about how slug-derived topics relate to an explicit query, or which takes precedence.

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+resource ('Returns recent news articles') scoped to a Polymarket market topic, which is clearly distinct from every sibling tool (all market/trader data). It stops short of an explicit contrast with siblings, but the resource itself is unambiguous.

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 clause 'useful for grounding LLM analysis' implies when to reach for it, but there is no explicit when/when-not guidance and no named alternative (e.g., get_market_summary) for cases where structured market data is wanted instead of news.

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