Skip to main content
Glama

Sciencebase

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

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

Annotations (readOnly, idempotent) are confirmed and description adds details: returns top-N tools with full schemas and curated examples, ready to call directly, no contradiction. Rich behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is dense but well-structured with a clear purpose, use cases, and output details. Each sentence adds value, though could be slightly more concise. Front-loaded purpose sentence.

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?

Given no output schema, description fully explains what is returned (names, descriptions, schemas, examples). For a flat schema with 6 params and moderate complexity, this is complete and actionable.

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%, so baseline is 3. Description adds aliases and examples but doesn't significantly extend meaning beyond what the schema already provides for each parameter.

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's purpose: 'Find tools by describing the data or task.' It uses a specific verb+resource and distinguishes itself from sibling tools by specifying it should be called first to browse the option set, unlike specific data tools.

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 'Use when you need to browse, search, look up, or discover what tools exist for:' followed by a list of domains, and instructs to call this first when many tools are available. Lacks explicit when-not or alternatives, but context makes it clear.

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

All Sciencebase 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
Disambiguation4/5

Most tools have distinctly described purposes, but there is some overlap among query tools like ask_pipeworx, ask_pipeworx_grounded, deep_research, and validate_claim, which could cause confusion for an agent.

Naming Consistency3/5

Tool names are consistently snake_case but vary in pattern: some are verb_noun (ask_pipeworx, compare_entities), while others are noun_noun (entity_profile, polymarket_arbitrage) or longer phrases (scan_competitor_ai_presence), making the naming system inconsistent.

Tool Count2/5

With 33 tools, the server feels over-scoped. Many tools are niche (e.g., polymarket-specific ones) and the high number exceeds the typical range for a focused server, leading to potential overwhelm.

Completeness3/5

The server covers a broad range of query and monitoring tasks for its domains, but lacks write operations (except memory tools). There are notable gaps like no tool for creating or editing ScienceBase items, which seems incomplete given the server's name.

Resources