Skip to main content
Glama

Conceptnet

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 readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds beyond this: explains the composite nature (fans out across deps.dev and bundlephobia), mentions partial failures and timing (bundlephobia first measurement 5-30s), and sources_failed list. No contradictions.

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 a single paragraph but dense with information. It front-loads the composite nature. While it could be broken into bullet points, it remains clear and efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description explains the return structure (summary block, per-advisory detail, links, alternative versions) and covers edge cases like partial failures. It is fairly complete.

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% with descriptions for both parameters. The description adds additional context: explains the default version behavior and that scoped packages are accepted, adding value beyond the schema.

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 as a composite check for npm packages covering license, advisories, and bundle size. It distinguishes itself from siblings by specifying the ecosystem (NPM) and mentioning alternative tools like deps.dev:version.

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?

The description explicitly says 'Use whenever an agent asks "is X safe / popular / small"...' It also notes limitations: NPM only in v1, and mentions partial failures. This provides clear when-to-use guidance.

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

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

Several tools have heavily overlapping purposes: ask_pipeworx, ask_pipeworx_beta, and ask_pipeworx_grounded are near-identical, and the five polymarket_* tools (arbitrage, edges, edge_tracker, fill_risk, kalshi_spread) all target prediction-market opportunities. The memory tools (remember/recall/forget) are distinct, as are subscriptions, but the routing and Polymarket clusters create real misselection risk.

Naming Consistency3/5

All names are snake_case, but the pattern is mixed: some are verb_noun (ask_pipeworx, compare_entities, discover_tools, resolve_entity), some are noun_verb or adjective_noun (bet_research, entity_profile, pipeworx_trending, recent_changes), and some are bare nouns/verbs (lookup, query, recall, relatedness). The 'polymarket_*' and 'ask_pipeworx*' families are consistent internally, but the overall set lacks a uniform verb-first convention.

Tool Count2/5

With 34 tools, the server is heavily over-scoped for a server named 'Conceptnet' — the vast majority of tools belong to a separate Pipeworx data-access product, not a semantic-network API. While each tool has a use, the count feels bloated and the server name misrepresents the actual surface.

Completeness4/5

The ConceptNet portion is complete (lookup, query, relatedness cover graph traversal). The Pipeworx portion is also fairly complete: universal router, grounded mode, deep research, entity profiles, comparisons, claim validation, subscription lifecycle, memory, and feedback. Minor gaps exist (e.g., no direct SEC filing fetch without going through ask_pipeworx), but the meta-tools mostly fill them.

Resources