Skip to main content
Glama

Magic 8 Ball

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 already indicate readOnly, openWorld, idempotent, non-destructive. The description adds valuable technical details: BGE-base-en embeddings, cosine similarity, 500-char overlapping windows, 200K char cap with truncation and flagging. This goes beyond annotations to inform agent behavior.

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?

The description is concise (two main sentences plus one technical detail sentence). It is front-loaded with the core purpose and then adds usage guidelines and technical specifics. No unnecessary words.

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?

The tool has no output schema, but the description explains the return format: top-N passages with character offsets and similarity scores. It also covers limits (200K chars), embedding model, and pairing with another tool, making the description self-contained.

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 the description's examples for 'query' and 'limit' are supportive but not essential. The description adds context like 'natural-language query' with examples, which slightly enhances understanding 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?

The description clearly states the tool performs semantic search inside a fetched record, with specific examples (SEC 10-K, article) and details like returning top-N passages with offsets. It distinguishes itself from sibling tools by focusing on searching inside existing data, not fetching new data.

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

Usage Guidelines4/5

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

The description explicitly says 'Use when the record is too big to cram into the prompt' and pairs with ask_pipeworx_grounded for grounding. It gives clear context but does not list when not to use or alternative tools explicitly.

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

All Magic 8 Ball 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.2/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, but the three ask_pipeworx variants (standard, beta, grounded) share similar routing and could cause confusion for an agent. The memory tools and novelty tool are distinct. Overall, ambiguity is low.

Naming Consistency4/5

Tool names follow a consistent snake_case verb_noun pattern (e.g., ask_pipeworx, compare_entities, subscribe). Minor deviations like 'search_within' and 'magic_8_ball_ask' do not break the pattern. High consistency.

Tool Count3/5

With 32 tools, the server is on the heavier side for a single MCP server. However, given the broad domain coverage (financials, economics, prediction markets, etc.), each tool serves a distinct purpose. Bordering on too many, but justified by scope.

Completeness4/5

The tool surface covers a comprehensive range of data research operations: querying, deep research, entity profiling, comparisons, discovery, subscriptions, alerts, claim validation, and prediction market analysis. Minor gaps exist (no data modification tools), but they are out of scope for a query-oriented server.

Resources