OSS license metadata + compatibility checker MCP server.
Four tools with clear verb-noun naming (lookup_, check_, list_, get_) and concise descriptions (50-90 chars). All have input schemas with required fields. However, parameter descriptions are sparse or missing entirely, most params lack guidance on format, constraints, or when to use them. Output schemas are undocumented; LLMs cannot predict response structure. Error handling returns JSON objects but lacks recovery guidance (e.g., 'not in cache' does not suggest next steps). No tool annotations (readOnlyHint, idempotentHint). Composition is sound, each tool has one responsibility and tools chain via SPDX IDs. Baseline: avg tool description 70 chars (within 10 - 1024 range), but 0% of params have descriptions (rubric baseline: 100% of A+ tools have param descriptions).
Can host license use dependency license? Returns compatible/conditional/incompatible + rationale.
What you must do / can do / cannot do under this license. Cited source URL.
All licenses compatible/conditional/incompatible with a host license.
Full SPDX license record — name, copyleft, obligations, OSI/FSF approved.
No parameter descriptions. All four tools have required params (spdx_id, host, dependency) with no guidance on format, valid values, or constraints. LLMs cannot infer whether 'MIT' or 'mit' is accepted, or what happens if an invalid SPDX ID is passed.
Output schemas undocumented. Tools return JSON objects with fields like 'snapshot_as_of', 'snapshot_source', 'served_by', 'compatible', 'conditional', 'incompatible', 'obligations', 'permitted', 'forbidden', but no schema definition tells LLMs what to expect. Agents cannot plan downstream calls or extract fields reliably.
Error responses lack recovery guidance. 'spdx_id not in cache' and 'pair not in matrix; check counsel' do not tell the LLM what to do next. Should suggest: 'Try a different SPDX ID' or 'Call list_compatible() to see available options'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 50 | 2026-07-28+ | v2 |
No tool annotations. Tools are read-only (no side effects) but lack readOnlyHint in schema. This prevents clients from optimizing caching, retry logic, or safety checks.
check_compatibility: 'dependency' parameter has no description. Is it a SPDX ID like 'MIT'? A package name? A version range? Ambiguity forces LLM guessing.