Skip to main content
Glama

Mfapi India

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

A5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds behavioral details: partial failures degrade gracefully, bundlephobia's first measurement can take 5-30s, sources_failed will list timed-out sources. 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?

Single paragraph that is front-loaded with core purpose. Every sentence adds value, covering scope, usage, return values, and error handling. 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?

No output schema exists, but the description fully explains return values (summary block with fields, per-advisory detail, links, alternative versions) and error handling. Given the tool's complexity and lack of output schema, this is complete.

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

Parameters5/5

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

Schema description coverage is 100%. Description adds meaning: 'package' accepts scoped npm packages, 'version' defaults to latest when omitted. This goes beyond the schema descriptions.

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 it is a composite check for evaluating npm packages covering licenses, advisories, version history, and bundle size. It distinguishes itself from sibling tools by specifying it is for the NPM ecosystem only and directing other ecosystems to 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?

Explicitly states when to use: when an agent asks 'is X safe/popular/small' or 'what does adding lodash cost me'. Also provides exclusion guidance: NPM ecosystem only in v1; PyPI/Maven/Cargo/Go fall under 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 Mfapi India 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.4/5.0
Disambiguation5/5

Each tool has a clear, distinct purpose. The various `ask_pipeworx*` variants are differentiated by mode (single vs grounded vs research). `get_nav_history` vs `latest_nav` serve different query granularities. Administrative tools like `remember`/`recall`/`forget` are clearly separate. No two tools overlap in functionality.

Naming Consistency4/5

Tool names follow a consistent snake_case convention and generally use `verb_noun` order (e.g., `ask_pipeworx`, `search_schemes`, `validate_claim`). A few exceptions like `entity_profile` (noun_verb) exist, but the pattern is mostly predictable.

Tool Count3/5

At 34 tools, the server is quite large, including many specialized tools (e.g., multiple Polymarket tools, administrative memory/subscription tools) that could arguably be split into separate servers. The number feels slightly excessive for a coherent, focused server.

Completeness5/5

The tool set covers an extraordinarily wide range of domains: company financials, SEC filings, FDA drugs, economic data, mutual funds, real estate, prediction markets, npm dependencies, AI visibility, and more. It also includes memory, subscription, and feedback mechanisms. There are no obvious gaps for the domains addressed.

Resources