Skip to main content
Glama

Materials

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".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint false. Description adds technical details: embedding model (BGE-base-en), window size (500-char overlapping), character cap (200K chars with truncation flag), and output features (character offsets, similarity scores). These go beyond annotations to inform agent of limitations and 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?

Four sentences, each carrying essential information: purpose, use case, paired tool, technical implementation details. Front-loaded with the core action. Zero redundant or irrelevant 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 necessary aspects for an agent: what the tool does, when to use it, how it works technically (embeddings, windows, truncation), output format (passages with offsets), and relationship to sibling tools. Although no output schema, the description adequately describes return values.

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% (3 params all described). Description provides concrete examples for 'text' (SEC 10-K) and 'query' (supply-chain risk, drug interactions). For 'limit', it mentions 'top-N passages' implicitly. This adds value beyond the schema's descriptions.

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 'Semantic search INSIDE a fetched record' and specifies the verb (search) and resource (a record's text). It distinguishes itself from siblings by explaining it is for sub-document retrieval and explicitly 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 states when to use: 'when the record is too big to cram into the prompt'. Describes alternative approach (grounding over passages vs. whole document) and names a sibling tool (ask_pipeworx_grounded) for the complete workflow.

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

All Materials 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.8/5.0
Disambiguation3/5

While many tools have detailed descriptions that help differentiate them, there is significant overlap among query tools like ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research. The prediction market tools also cluster together, making it challenging for an agent to quickly pick the right one without careful reading.

Naming Consistency4/5

Most tools follow a descriptive snake_case convention (e.g., ask_pipeworx, entity_profile, compare_entities). Minor deviations exist, such as 'ai_visibility_check' and 'deep_research', but overall the naming pattern is predictable and clear.

Tool Count3/5

With 33 tools, the server is larger than typical single-domain servers. While it supports a broad data platform, this count feels somewhat bloated and could benefit from consolidation, especially among overlapping query tools.

Completeness1/5

The server is named 'Materials' but contains only two materials-specific tools (materials_search, materials_stability). The remaining 31 tools cover unrelated domains (finance, economics, prediction markets, etc.), leaving the stated domain severely incomplete.

Resources