Skip to main content
Glama

Yesterdays Number

by io.github.pipeworx-io

Ask Pipeworx Beta

ask_pipeworx_beta
Read-onlyIdempotent

Beta version of ask_pipeworx: identical universal router (same 5,801 tools, same arguments, same response shape) with candidate routing improvements enabled live whenever one is under test. No candidate is active right now (the last was retired on outcome evidence 2026-07-26), so this currently matches ask_pipeworx exactly. Use it exactly like ask_pipeworx when you want the newest routing; results are compared against the stable router to decide what merges. Falls back to nothing — this IS a full working router, just the experimental edge.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for question.
textNoAlias for question.
inputNoAlias for question.
queryNoAlias for question.
promptNoAlias for question.
questionYesYour question or request in natural language. Accepts query, q, prompt, text, input as aliases.

Schema Changelog

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

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Description explains the beta behavior: candidate routing improvements may be enabled live, currently none are active, and it falls back to nothing because it is a full working router. Annotations already declare readOnly, openWorld, idempotent, and non-destructive, and the description does not contradict them; it adds useful context about experimental routing 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 tightly written and focused. Each sentence adds distinct information: beta status, identical interface, candidate routing behavior, current state, and usage guidance. No redundant or filler content.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers purpose, relationship to the stable sibling, current behavior, and usage instruction. It lacks explicit detail on response format or what happens when a candidate is active, but those are not critical for invoking the tool correctly given the similarity to ask_pipeworx.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already has 100% coverage with each alias documented as an alias for question, and the description does not add any parameter semantics beyond what the schema provides. The baseline of 3 applies because the schema fully documents the parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States it is a beta version of ask_pipeworx with identical universal routing (same 5,801 tools, same arguments, same response shape), which clearly distinguishes it from the stable sibling. It does not precisely describe what the router does beyond routing, but the comparison to ask_pipeworx makes the purpose clear.

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?

Explicitly says to use it exactly like ask_pipeworx when you want the newest routing and notes there is currently no candidate active, so results match the stable router. It does not explicitly mention when to prefer the stable sibling over this beta, but the beta-versus-stable context is clear.

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

All Yesterdays Number 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.9/5.0
Disambiguation3/5

Many tools have overlapping purposes, such as multiple query tools (ask_pipeworx, ask_pipeworx_grounded, deep_research) and prediction market analysis tools (bet_research, polymarket_arbitrage, polymarket_edges). While descriptions help differentiate, the clustering of similar functions may cause confusion.

Naming Consistency4/5

All tools use snake_case, but the pattern varies: some start with verbs (forget, remember, recall) while others start with nouns (entity_profile, pipeworx_trending). The naming is generally clear with minor inconsistencies.

Tool Count4/5

With 31 tools, the set is slightly large but appropriate given the broad scope covering company data, prediction markets, memory, subscriptions, and more. A few tools like yesterdays_number_get seem out of place, but overall the count is reasonable.

Completeness3/5

The tool set covers many domains comprehensively (SEC, FDA, FRED, prediction markets), but there are notable gaps such as no direct web search or stock price tool beyond routed queries. The server feels like a collection of capabilities rather than a unified domain.

Resources