Skip to main content
Glama

Data Cambridge

by io.github.pipeworx-io

Discover Tools

discover_tools
Read-onlyIdempotent

Find tools by describing the data or task. Use when you need to browse, search, look up, or discover what tools exist for: SEC filings, financials, revenue, profit, FDA drugs, adverse events, FRED economic data, Census demographics, BLS jobs/unemployment/inflation, ATTOM real estate, ClinicalTrials, USPTO patents, weather, news, crypto, stocks. Returns the top-N most relevant tools with names, descriptions, and full input schemas (with curated examples) — each result is ready to call directly, no second schema lookup needed. Call this FIRST when you have many tools available and want to see the option set (not just one answer).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoAlias for query.
taskNoAlias for query.
limitNoMaximum number of tools to return (default 20, max 50)
queryYesNatural language description of what you want to do (e.g., "analyze housing market trends", "look up FDA drug approvals", "find trade data between countries"). Accepts task, q, description, search as aliases.
searchNoAlias for query.
descriptionNoAlias for query.

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds that results are ready to call directly without extra schema lookup, and returns top-N relevant tools. 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?

Description is two sentences, front-loaded with purpose, uses a list of domains without verbosity. Every sentence contributes value.

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 discovery tool, the description explains return content (names, descriptions, schemas with examples) and when to use. No output schema exists, but the description implies the output format is sufficient for direct invocation.

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?

Schema coverage is 100% with detailed descriptions for each parameter. The description adds minimal extra context (e.g., 'top-N' implies 'limit') but nothing beyond what the schema already conveys. Baseline 3 is appropriate.

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 the tool finds tools by describing data or task, uses a specific verb ('find'), and distinguishes from siblings by being a meta-discover tool that returns other tools.

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 advises to call this first when many tools are available, and provides example use cases like 'analyze housing market trends'. It implicitly says not to use if already certain which tool.

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

All Data Cambridge 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

Most clusters have clear roles, and the detailed routing guidance separates ask_pipeworx from deep_research and grounded mode. However, three ask_pipeworx variants (one currently identical to stable), plus overlapping opportunity-discovery tools (polymarket_edges vs bet_research) and discovery/onboarding tools (discover_tools vs suggest_questions), leave several boundary cases where an agent could select the wrong tool.

Naming Consistency3/5

Many tools group under readable prefixes (ask_pipeworx, cambridge_, polymarket_, pipeworx_) and are mostly snake_case. But the set mixes bare verbs (remember, recall, forget), verb_noun actions (resolve_entity, validate_claim), and noun-phrase names (entity_profile, recent_changes, polymarket_fill_risk), so no single convention predicts the full API.

Tool Count2/5

34 tools is well into the 'too many' band, and the count is inflated by a kitchen-sink mix of data querying, prediction-market analysis, memory, subscriptions, feedback, llms.txt generation, and npm scanning. The server name 'Data Cambridge' suggests a narrow local-data scope, which makes the sprawl look even less appropriate.

Completeness3/5

Individual verticals are fairly complete: query/grounded/beta router levels, entity resolution/profile/compare/change, prediction-market discovery through fill-risk, and full memory and subscription CRUD. The major gap is discover_tools, which returns tools promoted as ready to call directly but no generic invocation tool is exposed, so the agent must route back through ask_pipeworx.

Resources