gridwork-license
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_licensesB | Scan a project's dependencies for license compliance issues. Detects copyleft conflicts, unknown licenses, and proprietary risks. Works with npm (node_modules), Python (requirements.txt), and more. |
| quick_checkB | Quick license overview — counts and risk breakdown without full details. |
| classify_licenseB | Classify a license string — returns risk level (copyleft, weak-copyleft, permissive, public-domain, proprietary, unknown) and SPDX identifier. |
| find_copyleftA | Find all copyleft-licensed dependencies in a project. Useful for quickly identifying viral license obligations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool targets a distinct operation: license string classification, copyleft discovery, quick overview, and full compliance scan. No functional overlap exists.
Three of four tools follow verb_noun pattern (classify_license, find_copyleft, scan_licenses). quick_check deviates slightly with adjective_noun, but remains clear and predictable.
Four tools cover the core license management tasks without redundancy. The count is well-scoped for the server's purpose.
Covers classification, copyleft identification, overview, and full scan. Minor gaps like license policy configuration or update capabilities could exist, but core workflows are complete.