Skip to main content
Glama

List npm package export targets

bpj_release_package_exports
Read-onlyIdempotent

Walk the exports conditions and fallback arrays of a package manifest, preserving each declaration path.

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_release_package_exports"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifestYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so the safety profile is covered. The description adds one real behavioral fact beyond that: it does not flatten or normalize declarations, it preserves every declaration path (including fallback arrays). However, with no output schema it never states the return shape (a list of targets? paths?).

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?

A single compact sentence with the resource front-loaded and no filler. It is efficient, though the terseness trades away specificity about what is returned.

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 simple read-only, one-parameter tool the description covers intent, but with no output schema the description should say what a caller receives (paths per condition/fallback branch). That return-value gap and the missing input-format note leave it adequate rather than complete.

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?

There is one parameter at 0% schema description coverage, so the description must carry the load. Saying it operates on "a package manifest" identifies the input semantically, but it does not state that the manifest is supplied as a JSON string with a 6000-character limit, nor how malformed input or condition ordering is handled.

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

Purpose3/5

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

The description names the operation and its resource: walking the exports conditions and fallback arrays of a package manifest while preserving each declaration path. That is more specific than restating the title, but the metaphor "walk" obscures that this tool enumerates/returns export targets, and nothing distinguishes it from siblings like bpj_release_package_name_shape.

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

Usage Guidelines2/5

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

The description gives no when-to-use guidance, no prerequisites (e.g. that the manifest must already be parsed JSON text), and no mention of alternatives or when not to use it. Usage is only inferable from the title and sibling names.

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.