Skip to main content
Glama

Group component license notices

bpj_release_license_notices
Read-onlyIdempotent

Group supplied component versions by license expression and mark missing declarations.

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

Input Schema

NameRequiredDescriptionDefault
componentsYes

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=true, idempotentHint=true, and closed-world, so the safety profile is covered. The description contributes the facts that grouping happens by license expression and that undeclared licenses get flagged, which is genuine added context. It says nothing about the shape of the returned grouping or how missing declarations are represented.

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?

One sentence, front-loaded with the primary verb and resource, with no filler. It is arguably too terse rather than too long, but structurally it is clean.

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

Completeness2/5

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

With no output schema and an entirely undescribed JSON-string input, the description should carry more weight than it does. An agent cannot reliably construct the required 'components' payload or anticipate the result from this text alone.

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?

The single parameter is an opaque JSON string titled 'Component metadata (JSON)' with 0% schema description coverage and a 6000-character cap. The description does not describe the expected JSON keys, the fields needed per component version, or the format of the license expression, which is exactly the information the schema omits.

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?

States a concrete verb ('Group') and resource ('supplied component versions') plus a secondary action ('mark missing declarations'), so the intent is legible. It stops short of explaining what 'mark' produces or how grouping is presented, so it is clear but not fully differentiated from other release-oriented siblings.

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?

There is no statement of when to use this versus alternatives, no preconditions, and no exclusions. The agent can infer it applies to license-notice generation from component metadata, but that is inference rather than guidance.

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.