Skip to main content
Glama

art

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 (readOnly, idempotent), the description reveals mechanics: returns passages with character offsets and similarity scores, uses BGE-base-en embeddings with 500-char overlapping windows, and has a 200K char cap with truncation flagged. This adds substantial operational context and does not contradict 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?

Three dense sentences: purpose, usage scenario, and technical limits. Every sentence earns its place, front-loaded with the core action, and avoids fluff. Highly efficient and well-structured.

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 search tool with no output schema, the description fully covers return format (top-N passages with offsets/scores), input expectations (text + query), and edge cases (truncation). It also situates the tool within the broader workflow via the sibling mention. The agent has everything needed to select and invoke correctly.

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 parameters are already documented. The description adds context for 'text' (e.g., 'already pulled' and truncation cap) and implies 'limit' via 'top-N passages.' It reinforces schema definitions without redundantly repeating them, but the added value is modest.

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 opens with 'Semantic search INSIDE a fetched record,' providing a specific verb and resource. It clearly distinguishes from sibling tools like ask_pipeworx by emphasizing searching within already-fetched text, with concrete examples (SEC 10-K, article).

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 this tool: 'Use when the record is too big to cram into the prompt.' It names a complementary sibling (ask_pipeworx_grounded) and explains how they pair, giving clear contextual guidance.

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

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

A3.5/5.0
Disambiguation2/5

Tools are a mix of art-related and Pipeworx data tools, with no clear boundary. Many Pipeworx tools overlap in functionality (e.g., ask_pipeworx, deep_research, bet_research), causing confusion. Art tools are distinct but sparse.

Naming Consistency2/5

Tool names mostly use snake_case but follow inconsistent patterns: some are verb-based (ask_pipeworx, search_artworks), others are noun-based (entity_profile, pipeworx_feedback). There is no unified convention across the server.

Tool Count1/5

33 tools is excessive for an art-focused server; only 4 tools (search_artworks, get_artwork, get_departments, generate_llms_txt) relate to art. The rest are from a different domain (Pipeworx), creating a severe scope mismatch.

Completeness2/5

For the art domain, only basic search and retrieval are provided; missing browsing, filtering, or creation tools. The Pipeworx tools are comprehensive but irrelevant to the server's stated purpose, leaving the art surface incomplete.

Resources