Skip to main content
Glama

Crontab

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.9/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive. The description adds substantial context beyond this: embedding model (BGE-base-en), cosine similarity over 500-char windows, 200K char cap with truncation flagging, and character offsets for verbatim quote verification. No contradiction with 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, front-loaded with the core purpose. Every sentence adds value: usage context, pairing with sibling, technical details. No fluff.

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 lacking an output schema, the description fully explains the return format (top-N passages with offsets and scores), parameter roles, input limits and truncation behavior, and integration with a key sibling tool. This is complete for a search tool.

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 is 3. The description adds semantic meaning beyond the schema: 'text' is 'text you already pulled', 'query' is a natural-language query with examples, and 'get back the top-N passages' clarifies how 'limit' behaves. This elevates it above the baseline.

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 a specific verb+resource: 'Semantic search INSIDE a fetched record.' It distinguishes itself from siblings by explicitly naming ask_pipeworx_grounded and describing its complementary role. The examples (SEC 10-K, article) make the purpose tangible.

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?

Provides explicit 'Use when...' guidance: when the record is too big to cram into the prompt. It also explains how it pairs with ask_pipeworx_grounded, giving clear context for when to choose this tool over alternatives like fetching the whole document.

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

All Crontab 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.6/5.0
Disambiguation2/5

Several tool clusters have blurred boundaries: ask_pipeworx_beta explicitly states it currently matches ask_pipeworx exactly, making them indistinguishable, and the five Polymarket tools (polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, bet_research, polymarket_kalshi_spread) all target prediction-market opportunities with overlapping concerns. The meta-tools (discover_tools, suggest_questions, pipeworx_trending) and entity tools (entity_profile, compare_entities, recent_changes) are better separated by their descriptions, but the identical beta/stable pair alone forces a low score.

Naming Consistency3/5

All tool names use snake_case, but the naming conventions are mixed: some follow verb_noun (describe_cron, next_runs, validate_claim), some are bare verbs (remember, recall, forget), and many are brand-prefixed noun phrases (ask_pipeworx, pipeworx_trending, polymarket_edges, bet_research). The pattern is readable and mostly predictable by prefix/domain, but there is no single consistent convention across the set.

Tool Count2/5

33 tools is above the reasonable threshold for a focused server, and the count is especially disproportionate for a server named 'Crontab': only 2 tools (describe_cron, next_runs) actually deal with cron, while roughly 24 tools are Pipeworx data-query, prediction-market, and memory utilities unrelated to the server's apparent purpose. The bulk of the tool surface feels like it belongs on a different server, making the count mismatched with the stated scope.

Completeness2/5

For a cron-focused server, the surface is incomplete: it can describe cron expressions and compute next runs, but has no tool to create, update, or delete a scheduled cron job — subscribe/unsubscribe manage data-event subscriptions, not cron schedules. The Pipeworx data side is broad (lookup, grounded verification, entity profiles, comparisons, research), but that completeness belongs to a different domain and does not rescue the cron purpose implied by the server name.

Resources