Skip to main content
Glama

Crystallography

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

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

Discloses partial failure behavior, timing (5-30s for first measurement), and graceful degradation. Annotations already indicate read-only and idempotent; description adds valuable context beyond them.

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?

Well-structured with clear sections (purpose, usage, return, limitations). Sentences are packed with information but not overly verbose. Could be slightly tighter by removing 'Composite' and 'in ONE call' as they are implicit.

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?

Comprehensive: covers return fields (is_latest, license, advisory_count, etc.), nested per-advisory detail, links, alternative versions, and failure behavior. No output schema, so description fully describes the output.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline 3. Description adds that scoped packages are accepted and version defaults to latest, going beyond the schema. Only minor room for improvement (e.g., expected format for version).

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 composite check for npm packages, listing specific sources (deps.dev, bundlephobia) and what it covers (license, advisories, bundle size). It distinguishes from sibling tools like scan_competitor_ai_presence.

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 tells when to use: 'Is X safe / popular / small' or 'what does adding lodash cost me'. Also specifies that PyPI etc. should go to deps.dev:version directly, providing clear exclusion guidance.

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

All Crystallography 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.7/5.0
Disambiguation2/5

There are three overlapping ask_pipeworx variants (stable, beta, grounded) plus a dense cluster of six polymarket trading/arbitrage tools, making misselection likely. Several other tools also blur together around research aggregation and entity lookup (entity_profile, compare_entities, recent_changes, validate_claim).

Naming Consistency3/5

All tool names are lowercase and snake_case, but the pattern is inconsistent: some are verb_noun (get_structure, resolve_entity), some are noun phrases (recent_changes, polymarket_edges), and a few are bare verbs (remember, forget, recall). The ask_pipeworx_beta/ask_pipeworx_grounded suffix pattern is readable but not mirrored across the rest of the set.

Tool Count2/5

34 tools is above the 25+ threshold for a server whose stated purpose is Crystallography, and only 3 of those tools actually serve that domain. The rest belong to Pipeworx data lookup, Polymarket betting, memory, research, subscriptions, and unrelated utilities, so the count feels excessive and the scope is unclear.

Completeness3/5

As a broad data-research toolset, there is decent lifecycle coverage: lookup, research, grounded verification, entity resolution, comparison, subscriptions, feedback, and memory all exist. However, for a server named Crystallography the domain surface is thin (search/get/get CIF only), and there is no general web-search fallback for topics not in the structured catalog.

Resources