Skip to main content
Glama

Wolfram Alpha

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. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive. The description adds significant behavioral context: fan-out across two services, partial-failure degradation, 5-30s first-measurement latency, sources_failed reporting, and full return field details. No contradiction with 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 appropriately sized for a composite tool. It front-loads the core purpose and then packs every sentence with actionable info: sources, use cases, return fields, ecosystem scope, and failure behavior. No wasted words.

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?

Given no output schema, the description enumerates the summary block fields, per-advisory details, links, and alternative versions. It also covers edge cases (first-version timeout, ecosystem fallback). This makes the tool fully self-contained for an agent to understand inputs, outputs, and failure modes.

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?

The input schema covers 100% of parameters with clear descriptions (npm package name, scoped packages accepted, version default). The description adds no new parameter-level meaning beyond the schema, so 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 states a specific composite check for npm packages ('should I add this npm package to my project') and names the data sources (deps.dev and bundlephobia). This clearly differentiates it from sibling research tools like deep_research or validate_claim.

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 provides when-to-use triggers ('Use whenever an agent asks "is X safe / popular / small"...') and an important exclusion ('NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly'). This gives agents clear decision criteria vs alternatives.

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

All Wolfram Alpha 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

Several tools are near-indistinguishable: ask_pipeworx and ask_pipeworx_beta are currently identical, and ask_pipeworx/ask_pipeworx_grounded/deep_research have overlapping routing behavior. discover_tools vs suggest_questions and ai_visibility_check vs scan_competitor_ai_presence also create boundary ambiguity, making misselection likely for agents.

Naming Consistency2/5

Names mix bare verbs (recall, remember, forget), brand-prefixed nouns (pipeworx_trending, polymarket_edges), and descriptive phrases (generate_llms_txt, scan_competitor_ai_presence). There is no consistent verb_noun or prefix convention, and the server name 'Wolfram Alpha' does not match the dominant pipeworx_/polymarket_ naming.

Tool Count2/5

At 34 tools, the set exceeds the 25+ threshold and feels heavy even for a broad data platform. Several unrelated add-ons (memory trio, ai_visibility, generate_llms_txt, scan_dependency) could live in separate servers, contributing to bloat and diluting the core purpose.

Completeness3/5

The data-research and prediction-market surfaces are fairly thorough (routing, grounded verification, deep research, entity resolution, comparisons, subscriptions), but the Wolfram Alpha core is thin—only short_answer, full_query, and wolfram_compute—with no step-by-step solutions, units catalog, or history. The mismatched server name and unrelated tools indicate an incoherent scope with notable gaps.

Resources