Skip to main content
Glama

Metabolights

by io.github.pipeworx-io

Pipeworx Trending

pipeworx_trending
Read-onlyIdempotent

What other AI agents are calling on Pipeworx right now. Returns the top tools, top packs, and total call volume over a recent window (24h, 7d, or 30d). Useful for: (1) discovering what data sources are hot for current events, (2) confirming a popular tool is the canonical choice before asking your own question, (3) seeing whether your use case aligns with what most agents need. Self-aggregating signal — derived from CF analytics-engine, no PII, just (pack, tool, count). Cached 5min-1h depending on window.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
windowNo24h (default) | 7d | 30d. Shorter windows surface what's hot right now; longer windows show steady-state demand.

Schema Changelog

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

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond annotations (readOnlyHint, etc.), description adds that data is self-aggregating from CF analytics-engine, no PII, and cached 5min-1h, providing valuable behavioral context.

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?

Concise and well-structured with bullet points. Every sentence adds value, though could be slightly more compact.

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 the simple tool (1 optional param, no output schema, rich annotations), the description fully covers purpose, usage, behavior, and parameter semantics.

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% with enum. Description adds meaning by explaining shorter windows surface hot topics and longer windows show steady-state demand, exceeding baseline of 3.

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 returns top tools, top packs, and call volume over a window, distinguishing it from siblings like discover_tools or ask_pipeworx by focusing on trending data.

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?

Identifies three specific use cases (discovering hot sources, confirming canonical choice, seeing alignment) but does not explicitly exclude when not to use it.

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

All Metabolights 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

B3.3/5.0
Disambiguation1/5

The vast majority of tools (e.g., ask_pipeworx, ask_pipeworx_grounded, bet_research, polymarket_arbitrage, etc.) are unrelated to Metabolights and overlap heavily with each other in purpose. Only two tools (get_study and search_studies) are clearly distinct and relevant to the server's stated domain.

Naming Consistency2/5

Tool names are highly inconsistent, mixing snake_case (get_study, search_studies), camelCase (ask_pipeworx), and varied verb styles (e.g., validate_claim vs bet_research). No consistent pattern across the set.

Tool Count1/5

With 28 tools, the server is extremely overpopulated for its stated purpose (Metabolights). Only 2 tools actually pertain to metabolomics study access, while the remaining 26 are general-purpose or unrelated (e.g., bet_research, polymarket_edges), making the count highly inappropriate.

Completeness1/5

The Metabolights domain severely lacks completeness: only search_studies and get_study are provided, with no create, update, delete, or upload functionality. The server fails to cover essential operations for its supposed domain.

Resources