Skip to main content
Glama

Inventory npm package scripts

bpj_inventory_package_scripts
Read-onlyIdempotent

Inspect package.json script names and their pre/post lifecycle hooks to check which scripts would run together.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "manifest": "<manifest>"
    },
    "name": "bpj_inventory_package_scripts"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds modest behavioral value by naming the lifecycle hook relationship it inspects, but it says nothing about error handling for malformed JSON, behavior when no scripts exist, or how deeply hooks are resolved.

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?

A single front-loaded sentence with no filler; the core action appears first and the purpose clause follows. Nothing in the wording is redundant or padded.

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

Completeness3/5

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

For a small single-parameter read tool with no output schema, the description covers the what but not the shape of the answer—an agent cannot tell whether it receives a flat list of names, a dependency map, or hook-annotated records. It is adequate but leaves the caller guessing at both input format and output structure.

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

Parameters2/5

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

Schema description coverage is 0% and the sole parameter 'manifest' is documented only by the generic title 'package.json contents' with a 9000-character cap. The description never mentions this parameter and gives no hint that an agent must supply the raw manifest text rather than a path or parsed object, leaving the most error-prone part of the call unaddressed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb+resource pair ('Inspect package.json script names') and narrows the scope to pre/post lifecycle hooks, which tells an agent exactly what data this tool surfaces. It doesn't differentiate against sibling tools, though the siblings listed are unrelated domain utilities, so there is little real overlap to disambiguate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The trailing clause 'to check which scripts would run together' implies the use case (understanding transitive script execution via pre/post hooks), which is genuinely helpful context. However, there are no explicit when-to-use/when-not-use rules, no stated prerequisites, and no guidance on what to do when the manifest is invalid or scripts are absent.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.