Skip to main content
Glama

Open Elevation

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.

Schema Changelog

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

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Discloses that it fans out to two external services, partial failures degrade gracefully, and the bundlephobia first measurement can take 5-30s. Adds value beyond annotations (readOnlyHint, idempotentHint) by explaining real-world behavior.

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 thorough but slightly long; however, every sentence adds value and front-loads the composite nature. Could be trimmed slightly but remains efficient for the complexity.

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, the description details the summary block contents, per-advisory detail, links, and alternative versions. Also covers edge cases like partial failures and timeouts. Fully complete.

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 coverage is 100%, and description adds context: scoped packages accepted, version defaults to latest if omitted. Provides clarity beyond the schema.

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 defines the tool as a composite check for evaluating npm packages, using deps.dev and bundlephobia. It distinguishes from siblings by focusing on a specific use case not covered by 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 states when to use ('is X safe / popular / small' or 'what does adding lodash cost me') and ecosystem limitations (NPM only in v1, with alternative for other ecosystems). Also notes potential delays and graceful degradation.

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

All Open Elevation 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 tool set covers many unrelated domains (elevation, finance, prediction markets, AI visibility, etc.) with multiple overlapping tools per domain (e.g., three 'ask_pipeworx' variants, several 'polymarket' tools). An agent would struggle to distinguish which tool to use for a given task.

Naming Consistency2/5

Names follow no consistent pattern: some use snake_case with vague verbs (e.g., 'process', 'run'), others use descriptive but unrelated prefixes ('ai_', 'ask_pipeworx_', 'polymarket_'). There is no uniform verb_noun structure.

Tool Count3/5

With 32 tools, the count is reasonable for a large server, but the vast majority are irrelevant to the server's stated purpose (elevation). This mismatch makes the count inappropriate.

Completeness1/5

The server name 'Open Elevation' implies a focus on elevation data, yet only 2 of 32 tools (get_elevation, get_elevations) are related. There are severe gaps: no area elevation, no geocoding, no terrain analysis. The tool surface is largely off-topic.

Resources