Skip to main content
Glama

Elife

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 declare readOnly, openWorld, idempotent, and not destructive. The description adds technical details beyond annotations: 'BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).' No contradiction.

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 a single paragraph, efficiently covering purpose, usage, behavior, and technical details. It is front-loaded with the main purpose and contains 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?

Despite no output schema, the description explains return values: 'top-N passages with character offsets and similarity scores.' It also mentions the 200K char cap and truncation behavior. This is complete for an agent to understand the tool's 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%, so baseline 3. The description adds meaning by explaining that 'text' is document text, 'query' is natural-language (with examples), and 'limit' is max passages. This adds value 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 'Semantic search INSIDE a fetched record' and explains the action: takes text and query, returns passages with offsets and scores. It distinguishes from sibling tools by specifying when to use it (when record is too large) and mentioning pairing 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?

The description explicitly provides usage guidance: 'Use when the record is too big to cram into the prompt' and explains how it pairs with ask_pipeworx_grounded for grounding over passages. This gives clear context and alternatives.

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

All Elife 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/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose. Tools like ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are differentiated by reliability mode; entity_profile vs compare_entities serve single vs multi-entity; and memorization, subscription, and search tools occupy separate operational niches. No two tools could be easily confused.

Naming Consistency2/5

Tool names follow no consistent pattern. Some use verb_noun (ask_pipeworx, resolve_entity, validate_claim), others are noun phrases (polymarket_arbitrage, ai_visibility_check), and some mix verb+noun with underscores inconsistently (generate_llms_txt, scan_competitor_ai_presence). This lack of uniformity makes the surface harder to navigate.

Tool Count3/5

34 tools is borderline high. The server spans multiple domains (data query, prediction markets, eLife, memory, subscriptions), and each domain gets several tools, making the overall surface feel bloated. While individual tools are justified, the total count strains discoverability and hints at scope creep.

Completeness2/5

The tool set is incomplete relative to its stated breadth. For a server named 'Elife', only 3 tools actually serve eLife; the rest are dominated by Pipeworx and Polymarket. Within the query/data domain, coverage is deep but lacks write/modify tools. Prediction market analysis lacks execution tools (no order placement). This leaves clear gaps for agents that need to act on the data.

Resources