Skip to main content
Glama

Pypi

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?

The description adds substantial context beyond annotations: chunking strategy (BGE-base-en, 500-char windows), character limit (200K chars with truncation flag), and return format (passages with offsets and similarity scores). Annotations only declare readOnlyHint, openWorldHint, etc.

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?

Two well-structured sentences plus technical details in a concise paragraph; front-loaded with the primary action, no extraneous content.

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 all essential aspects: purpose, usage, pairing, technical details, and return value (offsets, scores). No output schema exists, but the description adequately describes the output.

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 adds value by clarifying the max chars for text, providing example queries, and explaining the limit parameter. A baseline of 3 is exceeded.

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 specifies 'semantic search INSIDE a fetched record' with a clear verb and resource, and distinguishes itself from sibling tools like ask_pipeworx_grounded by explaining the pairing pattern.

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', and suggests pairing with ask_pipeworx_grounded, providing clear context for alternatives.

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

All Pypi 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 clearly distinct purposes, but some overlap exists among the polymarket tools (e.g., bet_research, polymarket_arbitrage, polymarket_edges) and the ask_pipeworx variants. The detailed descriptions help distinguish them, but an agent might still misselect in those groups.

Naming Consistency4/5

Tool names follow a mostly consistent verb_noun pattern in snake_case. Minor deviations exist, such as 'remember' vs 'recall' and the mixed use of verbs and nouns (e.g., 'ask_pipeworx' vs 'polymarket_arbitrage'), but overall the pattern is predictable.

Tool Count3/5

With 35 tools, the server is on the heavy side. While each tool serves a specific purpose, the sheer number may be overwhelming, and some subsets (like the 7 polymarket tools) could potentially be consolidated. Still, the scope justifies many of them.

Completeness4/5

The server covers a wide range of functionalities: Python package management, company research, prediction markets, monitoring, memory, and data queries. Minor gaps exist (e.g., no direct tool for editing subscriptions), but the surface is generally comprehensive and well-rounded.

Resources