Skip to main content
Glama

Geonames

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

A4.6/5.0
Behavior5/5

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

Adds behavioral context beyond annotations: partial failures degrade gracefully, bundlephobia first measurement can take 5-30s, and sources_failed will list timeouts while rest still returns. Annotations already indicate read-only, idempotent, non-destructive, so description adds specific failure details.

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?

Single dense paragraph with core purpose front-loaded and details following. Every sentence adds value, though the structure could be slightly more organized with bullet points. Still efficient and focused.

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?

Covers inputs, outputs, edge cases (partial failures, timeouts), ecosystem scope, and alternatives. Since no output schema exists, description compensates by detailing return format (summary block, advisories, links, versions). Complete for a composite tool.

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 description coverage is 100%, so baseline is 3. Description adds that scoped packages like '@types/node' are accepted for the 'package' parameter, but otherwise no significant enhancement beyond the schema's definitions. Meets but does not exceed baseline.

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?

Description specifies a composite check for npm packages including license, advisories, version history, bundle size, and more. It clearly states the verb 'check' and resource 'npm package', and distinguishes from siblings by noting NPM-only scope and alternative tools for other ecosystems.

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'. Also clarifies NPM-only in v1 and directs other ecosystems to deps.dev:version, providing clear when-not-to-use guidance.

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

All Geonames 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
Disambiguation2/5

Several tools have heavily overlapping purposes (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded; multiple polymarket_* scanners), and the mix of unrelated domains makes it hard to tell which tool is canonical for a task. The few geographic tools are distinct, but they are buried among dozens of non-geographic tools.

Naming Consistency2/5

Naming is a mix of verb_noun (search_geonames, resolve_entity), proper-noun prefixes (pipeworx_*, polymarket_*), and descriptive phrases (ask_pipeworx, bet_research, scan_competitor_ai_presence). No consistent pattern or verb style across the set.

Tool Count2/5

35 tools is far more than a Geonames-focused server needs, and most are unrelated to geospatial data. The count would be borderline for a general data platform, but it is excessive and unfocused for the stated server name.

Completeness1/5

The geographic surface is severely incomplete: only four tools (search_geonames, get_nearby, find_postal_codes, get_timezone) cover a tiny sliver of typical Geonames functionality like reverse geocoding, elevation, or distance calculations. The many non-geographic tools do not compensate for the missing core domain coverage.

Resources