Skip to main content
Glama

Arcgis Glasgow

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. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses partial failure behavior, the 5-30s first-measurement latency from bundlephobia, and the sources_failed field. This adds meaningful operational context without contradicting any annotations.

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?

The description is well-structured and front-loaded with the core purpose, then usage, returns, limitations, and failure handling. Every sentence earns its place; no fluff or redundancy despite being slightly long for a composite tool.

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?

For a complex tool with no output schema, the description thoroughly covers return summary fields, per-advisory detail, links, alternative versions, ecosystem constraints, timeout behavior, and partial failure semantics. It is complete for an agent to select and invoke correctly.

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 parameters are already well-documented. The description adds minimal new meaning beyond restating defaults and the npm ecosystem context; it mostly reinforces what the schema provides. Baseline 3 is appropriate.

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's purpose: a composite 'should I add this npm package' check that combines deps.dev and bundlephobia data. It specifies the verb ('scan'), the resource ('npm package'), and the unique composite nature, distinguishing it from any sibling 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?

Provides explicit when-to-use guidance: 'Use whenever an agent asks "is X safe / popular / small"...' It also gives a clear exclusion: 'NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly,' pointing to an alternative for non-npm packages.

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

All Arcgis Glasgow 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 unclear boundaries: ask_pipeworx, ask_pipeworx_beta (currently functionally identical), ask_pipeworx_grounded, deep_research, discover_tools, and suggest_questions all route to the same underlying catalog with only subtle differences. The Polymarket cluster (bet_research, polymarket_arbitrage, polymarket_edges, polymarket_edge_tracker, polymarket_fill_risk, polymarket_kalshi_spread) also substantially overlaps in purpose, and the two unrelated domains (GIS vs. data/betting) make it worse.

Naming Consistency3/5

Names are readable and form some predictable clusters (polymarket_* prefix, ask_pipeworx_* suffixes, subscribe/unsubscribe/list_subscriptions), but conventions are mixed: bare verbs (remember, forget, recall), noun_noun (layer_info, entity_profile, pipeworx_feedback), verb_noun (query_layer, search_datasets), and adjective_noun (deep_research, recent_alerts). No single pattern dominates, though nothing is chaotic.

Tool Count2/5

34 tools is well above the 25+ threshold for a heavy surface, and the count is not justified by the server's stated identity: only 3 of 34 tools (search_datasets, layer_info, query_layer) relate to ArcGIS Glasgow. The remaining 31 tools belong to several unrelated domains (Pipeworx data querying, Polymarket betting, AI visibility, memory, npm scanning), making the effective scope far too broad.

Completeness2/5

For the server's named ArcGIS Glasgow domain, the surface is thin: search, schema inspection, and query are present, but there is no way to list all datasets, no spatial querying, and no write/update capability. Meanwhile the 31 non-GIS tools create a sprawling second server's worth of functionality, so the set as a whole has no coherent domain whose coverage can be judged complete.

Resources