Read-only registry for agents.ml-nightworx.io. Discover ML-NIGHTWORX products, inspect capability eligibility, and get the next action. No authentication and no checkout.
Scored across 6 tools
The tools are mostly distinct: get_capability/get_product are ID-based reads, list_capabilities is a filtered list, and match_capability_to_intent is a router. get_catalogue overlaps somewhat with the list/read tools because it returns the full registry, but the descriptions make the intended granularity reasonably clear.
All tool names follow a consistent snake_case verb_noun pattern: get_, list_, and match_. The convention is predictable and readable throughout.
Six tools are well-scoped for a read-oriented registry intelligence layer. Each tool has a clear role: targeted reads, list/filter operations, catalogue access, engagement paths, and intent routing.
The surface covers the core read/query and routing workflows for a product-capability registry. A dedicated list_products or broader search operation appears to be a minor gap, though get_catalogue and product-filtered lists partially compensate.
Read a capability by canonical capability ID.
Inputs: id (required). Returns: id, name, tool, rules, +6 more
Read the full registry product, capability and indicative-offer catalogue.
Inputs: no named parameters. Returns: offers, version, products, conformance, +1 more
List service-only product engagement paths, optionally filtered by canonical product ID. Live products have no service-only engagement path.
Inputs: product. Returns: paths, catalogue_url, enquiry_email
Read a product by canonical product ID.
Inputs: id (required). Returns: id, url, name, status, +4 more
List registry capabilities, optionally filtered by canonical product ID and status.
Inputs: status, product. Returns: capabilities
Use the DEFAULT deterministic router to select navigation, engagement or clarification; no product execution.
Inputs: intent (required), context. Returns: match, status, product, rationale, +2 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Add one secure layer between your agents and this server.