Skip to main content
Glama

Odds Api

by io.github.pipeworx-io

Search Within a Source

search_within
Read-onlyIdempotent

Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe document text to search inside (max ~200K chars).
limitNoMax passages to return (1-20, default 5).
queryYesNatural-language query — what passages do you want? E.g. "supply-chain risk", "fiscal year 2024 revenue", "drug interactions with warfarin".

TDQS

A4.7/5.0
Behavior5/5

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

Annotations declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description goes beyond by detailing the embedding model (BGE-base-en), windowing strategy (500-char overlapping windows), character cap (200K chars with truncation and flagging), and the presence of character offsets for verification. No contradictions.

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 concise sentences that front-load the core purpose and then add key details. No unnecessary words or repetition. Every sentence adds value.

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

Completeness5/5

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

Given the tool's moderate complexity (3 parameters, annotations, no output schema), the description covers usage context, algorithm details, constraints, and integration with sibling tools. It is sufficiently complete for an agent to select and invoke correctly.

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?

Parameter schema coverage is 100%, so the description does not need to add much. It provides example queries and explains the purpose of text (e.g., SEC 10-K body), but the schema already describes each parameter sufficiently. Therefore, baseline score of 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?

The description clearly states the action (semantic search inside a fetched record), the input (text and natural-language query), and the output (top-N passages with offsets and similarity). It distinguishes itself from siblings like ask_pipeworx_grounded by focusing on searching within a single record rather than grounding over multiple passages.

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

Usage Guidelines5/5

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

Explicitly advises use when the record is too large for the prompt, saving context and returning only relevant passages. It also mentions pairing with ask_pipeworx_grounded for grounding, providing clear guidance on when to use this tool versus alternatives.

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

All Odds Api toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

Most tools have distinct scopes, and the long cross-referencing descriptions help a lot. However, ask_pipeworx_beta is currently an exact duplicate of ask_pipeworx by the server's own description, and the polymarket_* family plus ask_pipeworx/ask_pipeworx_grounded/deep_research have overlapping boundaries that could mislead an agent.

Naming Consistency4/5

The vast majority follow a clear verb_noun snake_case pattern like get_odds, list_sports, resolve_entity, and subscribe. A few exceptions such as odds_api_quota, pipeworx_feedback, polymarket_arbitrage, and recall break the pattern slightly, but the overall convention is predictable.

Tool Count2/5

37 tools is well past the 25+ threshold and feels bloated for a server named 'Odds Api'. Many tools are meta-platform utilities — memory, feedback, trending, dependency scanning, llms.txt generation — that have no obvious connection to an odds API and make the surface hard to navigate.

Completeness4/5

The odds domain is well covered: list_sports, get_events, get_odds, get_event_odds, get_scores, quota tracking, and subscriptions form a coherent read/monitor workflow. Minor gaps exist — no historical odds or a single-event detail endpoint — but agents can complete core odds research and monitoring tasks without dead ends.

Resources