Skip to main content
Glama

polymarket-odds-prediction-market-events-mcp

search_endpoints

Read-only

Search 136 real-time APIs across x, search, social, commerce, b2b, finance, local, intel. Returns id, price_usd, p50_ms, summary.

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

Input Schema

NameRequiredDescriptionDefault
queryNoKeyword (e.g. youtube transcript, tweets, sec filings, seo)
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read, so the description's main added value is the return shape (id, price_usd, p50_ms, summary), which is genuinely useful since no output schema exists. It says nothing about result limits, ranking, pagination, or whether the 136 count is fixed, leaving real behavioral gaps.

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?

Two compact sentences, front-loaded with the capability and followed by the return fields. The category enumeration is a bit listy but it is informative rather than filler, and there is no redundant restatement of the title.

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

Completeness3/5

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

For a two-parameter discovery tool with no output schema, disclosing the returned fields is the right call and largely fills the gap. What remains missing is how results should be used downstream (schema lookup before invocation) and any note on result volume or ranking, which matters for a 136-item catalog.

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 50% schema coverage, the query parameter carries a description with keyword examples while category is a self-documenting enum. The description's category list mirrors the enum values rather than adding new meaning, so it does little to compensate for the partial coverage gap.

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 and resource ('Search 136 real-time APIs') and enumerates the eight categories covered, so an agent immediately knows this is a catalog-discovery tool. It does not explicitly contrast itself with siblings such as call_endpoint or get_endpoint_schema, which keeps it short of a 5.

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 when-to-use or when-not-to-use guidance, and no mention of how this fits relative to call_endpoint or get_endpoint_schema. An agent must infer that searching precedes schema lookup and invocation, which is a reasonable inference but not stated anywhere in the text.

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