Skip to main content
Glama

bouncer_check_manifest

Read-only

Check which dependency versions npm would install from a package.json before running npm install, flagging BLOCK or REVIEW results with reasons and safe versions.

Instructions

Checks every dependency in a package.json at the version npm would install for its range today (the newest match), e.g. before running npm install in a cloned repo. Runs as an MCP Task with live progress; returns BLOCK/REVIEW first, each with the reason and a safe version.

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": {
      "packageJson": "<packageJson>"
    },
    "name": "bouncer_check_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeDevNoAlso check devDependencies
packageJsonYesThe full text of package.json (up to 90 KB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / packageJson / description
      Previous value: -"The full text of package.json"New value: +"The full text of package.json (up to 90 KB)"
    • changedInput schema / properties / packageJson / maxLength
      Previous value: -200000New value: +90000
  2. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds meaningful behavioral context: it runs as an MCP Task with live progress, and the return payload leads with BLOCK/REVIEW entries each carrying a reason and a safe version. That output-ordering and async-execution detail is real value beyond annotations, though it doesn't cover latency, result size, or what REVIEW implies operationally.

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?

Two sentences, front-loaded with purpose and scope, then the usage cue and return contract. No filler, and every clause contributes information the agent needs.

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?

With no output schema, the description carries the return-value burden and does so partially — it names BLOCK/REVIEW, ordering, reasons and safe versions. What BLOCK versus REVIEW means for the caller's next action, and whether the result also lists passing dependencies, is left implicit, which is the only real gap for a tool of this complexity.

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 description coverage is 100%, with both parameters documented inline (including the 90 KB cap and the includeDev devDependencies behavior). The description adds no parameter-level detail, so the baseline of 3 applies.

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?

States a specific verb and resource ('Checks every dependency in a package.json') plus a precise scope qualifier — the version npm would install for the range today, i.e. newest match. This distinguishes it from siblings like bouncer_check_package and bouncer_check_upgrade, which operate on different inputs or questions.

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

Usage Guidelines4/5

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

Gives a concrete triggering scenario — 'before running `npm install` in a cloned repo' — so the agent knows the intended moment of use. It does not, however, name an alternative sibling or state when not to use it, which keeps it short of a 5.

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