Skip to main content
Glama
ellmos-codecommander-mcp

ellmos-codecommander-mcp

Generate Licenses

cc_generate_licenses
Idempotent

Generate a third-party license file for npm or Python projects by reading dependency manifests and collecting license data into text, JSON, or CSV formats.

Instructions

Generates a third-party license file for an npm or Python project.

Args:

  • project_dir (string): Project directory

  • output_path (string): Output file

  • format (string): "text" | "json" | "csv"

Reads package.json (npm) or pip packages and collects license info.

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": {
      "project_dir": "<project_dir>",
      "output_path": "<output_path>"
    },
    "name": "cc_generate_licenses"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNoFormattext
output_pathYesOutput file
project_dirYesProject directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.3.27
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.3.8

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds the data sources it scans, but does not say whether output_path is created or overwritten, which matters given the write hint and the idempotency claim.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded and useful, but the Args block duplicates parameter names and descriptions already in the schema, spending roughly half the text on redundant content.

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?

With three simple parameters, annotations, and no output schema, the definition covers the essentials. It omits how the tool resolves the project type or behavior when no manifest/lockfile is found, which is the main open question for a file-writing generator.

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% and the enum/default are declared in the schema, so the 'Args' block largely restates structured data. It adds no format-selection guidance (e.g., what json/csv output contains) beyond what the schema already provides.

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 first sentence gives a specific verb and resource ('Generates a third-party license file') plus the supported ecosystems (npm, Python). It is unmistakable against the sibling list, none of which do licensing, though it does not explicitly contrast with them.

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?

'Reads package.json (npm) or pip packages' implies the prerequisite context (an npm or Python project) but never states when to use this versus other tooling, nor what happens with unsupported project types. Usage is inferable rather than specified.

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