Skip to main content
Glama

Cbioportal

by io.github.pipeworx-io

What Can I Ask Pipeworx?

suggest_questions
Read-onlyIdempotent

What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass topic (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNoOptional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread.

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint. The description adds valuable context on return format (category-bucketed examples with tool+argument shape) and that it draws from a live catalog, enhancing behavioral understanding.

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?

The description is front-loaded with alternative queries and efficiently covers purpose, usage, and return format. Some redundancy exists but serves clarity; it earns its length.

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?

With no output schema, the description adequately explains the return type (category-bucketed examples with tool+argument shape) and covers all aspects of usage: when to call, arguments, and purpose.

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 a description for `topic`. The description reiterates and provides examples like 'finance', 'pharma', 'betting', adding slight value but not substantially exceeding schema information.

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 category-bucketed example questions with exact tool and argument shapes, serving as an onboarding entry point. It distinguishes itself from siblings by being the first tool to use when unfamiliar with Pipeworx capabilities.

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?

The description explicitly says 'Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools.' It also explains when to omit `topic` for full spread or pass a specific topic to focus, providing clear usage context.

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

All Cbioportal 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
Disambiguation3/5

Most tools have clearly distinct purposes, but ask_pipeworx_beta is an intentional near-duplicate of ask_pipeworx, and several polymarket/entity tools overlap in scope. The descriptions do enough to disambiguate most pairs, but the duplicate beta routing tool introduces real ambiguity.

Naming Consistency3/5

All names use snake_case, but the pattern varies: verb_noun (get_gene, search_studies), noun_noun (polymarket_edges, pipeworx_trending), and product-prefixed verbs (ask_pipeworx, bet_research). There is no single consistent convention, though the names remain readable.

Tool Count2/5

35 tools is a heavy surface, and the vast majority (31) are unrelated to cBioPortal; only four tools actually belong to the named domain. This makes the count inappropriate for a cancer-genomics MCP server, as the set is bloated with out-of-scope utilities.

Completeness1/5

For a cBioPortal server, only metadata-level tools exist (gene lookup, study details, cancer types, study search); core cBioPortal data access — mutations, copy-number alterations, clinical data, molecular profiles, sample-level queries — is entirely missing. The tool surface severely under-covers the named domain.

Resources