Skip to main content
Glama

Check common npm package name syntax

bpj_release_package_name_shape
Read-onlyIdempotent

Check common lowercase ASCII new-package syntax, including scope, reserved names and length.

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

Input Schema

NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds what is actually validated (lowercase ASCII, scope, reserved names, length) and the hedge 'common' signals the check is approximate. It does not say what a failure looks like or whether the result is a boolean, an error string, or a list of violations.

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 compact sentence with the resource and the covered rules front-loaded; every clause adds information and nothing is padding.

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?

The tool is simple (one string in, no nested objects), but with no output schema the description should say something about the return shape for a pass/fail validator. As written, an agent knows what is checked but not what comes back or how strictly 'common' limits the check.

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?

With one parameter and 0% schema description coverage, the description must carry the burden; it does explain that the input is a package name subject to lowercase ASCII, scope, reserved-name, and length rules. However, it does not clarify the expected string form — e.g. whether a scoped name should include the '@scope/' prefix or a version suffix — which is exactly the ambiguity that matters for this validator.

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 names a specific verb ('Check') and resource ('lowercase ASCII new-package syntax') and enumerates the rules covered: scope, reserved names, and length. It is clearly distinct from siblings like bpj_dq_email_shape or bpj_dq_identifier_shape by virtue of the npm package-name domain, though it never explicitly contrasts itself with those shape validators.

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?

Usage is only implied: the word 'new-package' suggests this is for validating a proposed package name rather than an existing one, and 'common' hints it is not a full npm spec check. There is no explicit when-to-use statement, no exclusion, and no pointer to an alternative validator.

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.