Skip to main content
Glama

Arcgis Longview

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.6/5.0
Behavior5/5

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

Beyond readOnly/idempotent annotations, it discloses partial failure degradation, the 5-30s first-measurement delay, and the sources_failed field. This is valuable operational context.

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 slightly long but every sentence adds value. It's front-loaded with the core purpose and then covers use cases, return structure, and failure modes in a logical flow.

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 composite tool with no output schema, the description enumerates all return fields (summary block fields, advisories, links, alternatives) and explains edge cases (partial failures, ecosystem limits). This is complete for an agent to 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 coverage is 100%, so the description adds little beyond the schema. It does mention scoped packages and version default, but these are already in the schema. 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 opens with a specific composite check, naming deps.dev and bundlephobia and clearly stating it evaluates npm packages. This distinctively separates it from sibling tools, which focus on AI visibility or market edges.

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?

It explicitly states when to use ('is X safe / popular / small', 'what does adding lodash cost me') and gives an exclusion: non-NPM ecosystems should go to deps.dev:version directly.

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

All Arcgis Longview 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

A4/5.0
Disambiguation3/5

Descriptions are unusually explicit about when to use each tool (single lookup vs grounded vs deep research), but the set still contains several genuinely overlapping tools: ask_pipeworx_beta is explicitly identical to ask_pipeworx, scan_competitor_ai_presence wraps ai_visibility, and six polymarket_* tools share the same 'edge/arbitrage' conceptual space. An agent can usually pick the right tool but faces real ambiguity in several clusters.

Naming Consistency4/5

Names are uniformly snake_case and readable, and there are coherent prefix families (ask_pipeworx_*, polymarket_*, pipeworx_*). However the verb placement is inconsistent: verb_noun (ask_pipeworx, validate_claim, discover_tools) coexists with noun-first names (recent_changes, entity_compare, layer_info, polymarket_edges), and bet_research sits outside the polymarket_* family despite being a prediction-market tool.

Tool Count2/5

34 tools is well past the 'feels heavy' threshold, and more importantly the set mixes what looks like three different servers: a tiny ArcGIS/Longview GIS slice (layer_info, query_layer, search_datasets), a massive general-purpose data-research platform from Pipeworx, and a Polymarket prediction-market toolkit. Most tools earn their place for the platform, but far too few belong to the named domain.

Completeness4/5

The research surface is remarkably complete: a router, grounded and beta variants, deep multi-source research, claim verification, entity/profile/change resolution, discovery and suggestion helpers, memory (remember/recall/forget), subscriptions (subscribe/unsubscribe/recent_alerts), and feedback — no obvious lifecycle dead ends. Minute gaps exist on the GIS side (no dataset editing, no metadata browsing, no named export/view ops) and a few nooks like screen- leisure tools have no progress/status endpoints, but these are workaroundable.

Resources