Skip to main content
Glama

Openiban

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?

Annotations already declare read-only, idempotent, and non-destructive behavior; the description adds valuable context beyond that: composite fan-out across multiple sources, a 5-30s latency warning for bundlephobia's first measurement, graceful partial-failure handling with a sources_failed field, and a detailed list of what the summary block contains. This is substantial behavioral disclosure.

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 three sentences, front-loaded with the core purpose, then usage triggers, then return details and limitations. Every sentence earns its place; it is compact yet comprehensive, with no filler.

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 having no output schema, the description fully specifies return values (summary fields, per-advisory detail, links, alternatives). It covers purpose, usage timing, ecosystem limitations, latency, and failure behavior, making it complete for agent decision-making. Complexity is high, but the description compensates well.

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%, with both 'package' and 'version' fully described. The description does not add substantive new meaning beyond the schema (it mentions version defaults but that's already in the schema). Baseline of 3 is appropriate since schema carries the load.

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 verb+resource+outcome: a composite 'should I add this npm package to my project' check. It clearly distinguishes itself from sibling tools by detailing the data sources (deps.dev + bundlephobia) and the NPM-only scope, making its unique purpose unmistakable.

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 usage guidance is provided with direct trigger examples ('is X safe / popular / small' or 'what does adding lodash cost me'). It also states an exclusion and alternative for non-NPM ecosystems, pointing to deps.dev:version directly, which helps an agent choose between this and other tools.

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

All Openiban 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

Multiple tools have heavily overlapping purposes: ask_pipeworx and ask_pipeworx_beta are explicitly identical right now, and the polymarket_* family (edges, arbitrage, edge_tracker, fill_risk) blurs together for an agent trying to pick one. entity_profile and recent_changes also both pull company data, and ai_visibility_check vs scan_competitor_ai_presence are single-vs-multi variants of the same probe.

Naming Consistency3/5

Naming is mostly snake_case and readable, with many verb_noun forms (validate_iban, generate_llms_txt, resolve_entity). However, there are bare verbs (remember, forget, recall, subscribe, unsubscribe), noun phrases (entity_profile, recent_changes, pipeworx_trending), and inconsistent prefixes (ask_ vs polymarket_ vs suggest_) that break a clear pattern.

Tool Count3/5

33 tools is borderline-heavy for a data-research API, but the bigger issue is that the server is named Openiban yet contains only two IBAN tools and 31 unrelated Pipeworx/data tools. The count feels bloated and misaligned with the server's apparent identity, though not extreme enough for a 1 or 2.

Completeness2/5

For the Pipeworx data-research domain the surface is quite rich (query, deep research, entity profiles, comparisons, subscriptions, memory). For the server's stated IBAN purpose, only validate and suggest_iban exist — no generation, parsing, batch checks, or bank detail coverage — so the tool set is severely incomplete relative to the server name.

Resources