Skip to main content
Glama

Cbioportal

by io.github.pipeworx-io

Scan Dependency

scan_dependency
Read-onlyIdempotent

Composite "should I add this npm package to my project" check in ONE call — fans out across deps.dev (license + advisories + version history) and bundlephobia (gzipped/minified bundle size, dependency count, ESM/tree-shake support). Use whenever an agent asks "is X safe / popular / small" or "what does adding lodash cost me". Returns a summary block (is_latest, license, published_at, advisory_count, bundle_kb_min, bundle_kb_gz, dependency_count, has_esm, tree_shakeable), per-advisory detail, links, and a list of recent alternative versions. NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly. Partial failures degrade gracefully — bundlephobia's first measurement on a new version can take 5-30s; sources_failed will list it if it times out, the rest still returns.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
packageYesnpm package name. Scoped packages (e.g. "@types/node") are accepted.
versionNoSpecific version to check (e.g., "18.3.1"). Defaults to the latest published version when omitted.

TDQS

A5/5.0
Behavior5/5

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

Annotations already mark it as read-only, idempotent, non-destructive. Description adds critical behavioral context: partial failures (bundlephobia first measurement takes 5-30s, sources_failed field), and that it fans out across two services. No contradictions.

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?

Concise yet comprehensive. Front-loaded with core purpose and returns. Every sentence adds value—ecosystem scope, timing notes, fallback behavior. No wasted words.

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?

Despite no output schema, description fully explains the return structure (summary block fields, per-advisory detail, links, alternatives). Complex composite tool with adequate coverage of parameters, behaviors, and edge cases.

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

Parameters5/5

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

Schema description coverage is 100% for both parameters. Description adds useful nuance: scoped packages accepted for 'package' and default behavior for 'version' (latest when omitted).

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 it is a composite check for npm packages, combining deps.dev and bundlephobia data. It specifies the exact use case ('is X safe / popular / small') and return values (summary block, advisories, links). No sibling tool duplicates this functionality.

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?

Explicit guidance on when to use ('agent asks about safety/popularity/size/cost') and ecosystem limitations (NPM only v1; alternatives like deps.dev:version for PyPI etc.). Also describes graceful degradation for bundlephobia timeouts.

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