Skip to main content
Glama

Prayer Times

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

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint. Description adds significant behavioral context: composite fan-out, partial failures degrade gracefully (sources_failed listed), bundlephobia first measurement can take 5-30s, and details on return structure (summary block, per-advisory, links, alternatives). No contradictions 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is comprehensive but not overly verbose. It front-loads the main purpose and then packs behavioral details, return structure, and limitations. Every sentence adds value, though slightly long. Could be trimmed slightly without losing substance.

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 rich annotations (readOnlyHint, openWorldHint, etc.) and no output schema, the description fully covers return values (summary block with fields, per-advisory detail, links, alternative versions) and behavior (partial failures, timing). Complete for the tool's complexity and ecosystem restrictions.

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?

Schema coverage is 100% with descriptions for both parameters. Description adds minor value: for 'package' mentions scoped packages accepted, for 'version' mentions defaults to latest when omitted. Baseline 3 is appropriate; schema already provides full meaning.

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?

Description clearly states it's a composite check for npm packages combining deps.dev (license, advisories, version history) and bundlephobia (size, deps, ESM/tree-shake). Specifies verb 'scan' and resource 'dependency' (npm). Distinguishes from siblings by noting NPM-only vs. other ecosystems under deps.dev:version directly.

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: 'when an agent asks is X safe / popular / small or what does adding lodash cost me'. Also gives when-not: 'NPM ecosystem only in v1; PyPI / Maven / Cargo / Go fall under deps.dev:version directly', providing clear exclusion and alternative.

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

All Prayer Times 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.8/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, though there is some overlap between `ai_visibility_check` and `scan_competitor_ai_presence`, and between `bet_research` and `polymarket_edges`. Overall, an agent can distinguish them.

Naming Consistency3/5

Tool names follow snake_case but vary in prefix usage (e.g., `pipeworx_*`, `polymarket_*`, no prefix) and verb presence (e.g., `discover_tools` vs. `generate_llms_txt`). The pattern is readable but inconsistent.

Tool Count2/5

With 24 tools, the server is overloaded for the 'Prayer Times' name. Many tools are unrelated to prayer, suggesting poor scoping relative to the server's implied purpose.

Completeness2/5

For prayer times, the server includes core tools but lacks features like multi-day forecasts or advanced settings. However, the inclusion of many unrelated tools makes the set incoherent and incomplete for any single domain.

Resources