Skip to main content
Glama

Predictit

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?

Beyond annotations (which already declare safe, idempotent, read-only), the description discloses internal mechanics (BGE-base-en embeddings, 500-char windows, cosine similarity), limits (200K chars with truncation flag), and output details (character offsets, similarity scores). No contradiction with annotations.

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?

Compact, front-loaded sentence defining the tool, followed by specific advice on usage, pairing, and technical details. No redundant sentences; every line earns its place.

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?

For a tool with no output schema, the description adequately explains return format (passages, offsets, scores), limits, and pairing strategy. All key aspects are covered.

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%, so baseline is 3. The description adds value by providing concrete query examples and clarifying the text cap, slightly enhancing beyond the 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 clearly states it performs semantic search inside a previously fetched record, using a natural-language query to return relevant passages. It distinguishes itself by specifying it works on already-fetched text, not on external searches, and pairs with 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 tells when to use: when the record is too large for the prompt. Provides a concrete alternative and pairing: use with ask_pipeworx_grounded for grounded queries instead of whole document.

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

All Predictit 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

A4.1/5.0
Disambiguation4/5

Most tools have distinct purposes, but pairs like ask_pipeworx/ask_pipeworx_grounded and bet_research/polymarket_edges could cause confusion without careful reading. Overall, descriptions are clear enough to differentiate.

Naming Consistency3/5

Names are snake_case and mostly follow verb_noun pattern, but several are noun_noun (entity_profile, pipeworx_feedback, polymarket_arbitrage) creating inconsistency. Still readable due to descriptive terms.

Tool Count4/5

33 tools is slightly high but justified given the broad scope (data retrieval, prediction markets, memory, subscriptions). Each tool serves a specific role, so the count feels appropriate for the platform's capabilities.

Completeness4/5

The tool set covers data retrieval, prediction market analysis, memory management, and subscriptions well. Minor gaps exist (e.g., no direct betting tool), but core workflows are supported comprehensively.

Resources