Skip to main content
Glama

Bhagavad Gita

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 failures (sources_failed), bundlephobia latency (5-30s on new version), and graceful degradation. Adds behavioral context beyond annotations (which already mark it as read-only, idempotent, etc.). No contradiction.

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?

Description is comprehensive but somewhat long. However, every sentence earns its place, starting with core purpose. Could be slightly tighter, but still effective.

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?

Covers all key aspects: multisource, output format (summary block, per-advisory, links, alternatives), error handling, and ecosystem scope. No output schema needed because return is explained.

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 is 3. Description adds value by clarifying version defaults to latest and scoped packages are accepted. No need to repeat schema details.

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?

Clearly states composite check for npm packages via deps.dev and bundlephobia, with specific verb 'scan' and resource 'dependency'. Distinguishes from siblings by focusing on npm ecosystem and package cost/safety evaluation.

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 notes NPM-only in v1 and directs other ecosystems to deps.dev:version directly, providing clear scope and exclusions.

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

All Bhagavad Gita 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
Disambiguation4/5

Individual tools have detailed descriptions and mostly distinct purposes, but the mix of domains (scripture, finance, data lookup) could confuse an agent about which tool to choose for a given task. However, within each subdomain, tools are clearly differentiated.

Naming Consistency2/5

Tool names follow no consistent pattern: some are verb_noun (ask_pipeworx, compare_entities), some are noun_verb (entity_profile, recent_changes), and some are single verbs (forget, recall). The mix of snake_case with varied starting parts makes naming unpredictable.

Tool Count1/5

With 23 tools but only 3 related to the server's stated purpose (Bhagavad Gita), the tool count is severely mismatched. The vast majority belong to data analytics and finance, making the set feel bloated and mis-scoped.

Completeness1/5

For a Bhagavad Gita server, only list_chapters, get_chapter, and get_verse are provided, missing obvious features like search, commentary comparison, or multiple translations. The other tools are irrelevant to the domain, leaving it extremely incomplete.

Resources