Skip to main content
Glama

Polygon Io

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.9/5.0
Behavior5/5

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

Annotations already provide readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds valuable behavioral details: BGE-base-en embeddings, cosine similarity, 500-char overlapping windows, 200K character cap with truncation flag, and character offsets on passages.

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?

Four dense sentences with zero waste. Front-loads purpose and usage, then technical details. 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?

Covers purpose, when to use, technical behavior (embeddings, windows, cap), pairing with sibling, and return value format. No output schema but mentions passages with offsets and scores, which suffices.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% but description enriches each parameter: explains text max length, query as natural-language with examples, and limit default and range. Adds context beyond schema.

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?

Description starts with 'Semantic search INSIDE a fetched record', clearly stating the verb (semantic search) and resource (inside a fetched record). Provides examples like SEC 10-K body and distinguishes from sibling ask_pipeworx_grounded.

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 states when to use: 'when the record is too big to cram into the prompt'. Also pairs with ask_pipeworx_grounded, giving clear alternative usage context.

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

All Polygon Io 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

B3.2/5.0
Disambiguation3/5

Tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded have overlapping purposes (all answer questions via a universal router), with only subtle distinctions (beta version, grounded mode). Additionally, many tools like entity_profile, compare_entities, recent_changes, and resolve_entity all pull SEC/company data, and polymarket_arbitrage, polymarket_edges, polymarket_fill_risk, bet_research all relate to prediction markets, creating potential confusion. However, each tool does have a somewhat distinct purpose and detailed descriptions help differentiate them, so it's not extreme overlap.

Naming Consistency2/5

Tool names are mostly lowercase with underscores (e.g., 'ask_pipeworx', 'compare_entities', 'resolve_entity'), but there's a mix of verb-first (bulk_splits, list_subscriptions) and noun-first (data_types, get_quote) patterns. Also 'aggregates' and 'grouped_daily' both fetch bars but have different naming styles. The naming is inconsistent with no clear uniform pattern, and some names are vague like 'helpers' or 'utility-*'.

Tool Count2/5

43 tools is quite heavy for a single MCP server, exceeding the typical 15-25 range for 'too many'. While the server aggregates many different domains (Polygon stocks, Pipeworx data, Polymarket, npm, etc.), the sheer number makes it overwhelming for an agent to discover and select the right tool. Many tools are meta-tools (ask_pipeworx, discover_tools) that add complexity rather than mapping to a clear domain.

Completeness4/5

The server covers a huge range of operations: stock data (retrieve, search, details), prediction markets (arbitrage, edges, research, fill risk), entity resolution, subscriptions, memory, and meta-tools. There are some gaps like no obvious tool for modifying stock data (not expected) and the Polymarket side lacks a tool for placing actual trades or managing positions. But overall the surface is quite complete for a comprehensive data/research server.

Resources