AXL MCP

The tools fall into clear families—routing/discovery, schema introspection, image operations, and generic execution—and the descriptions are unusually explicit about when each should be used. A few near-neighbor pairs like get_scenario_node_schema vs check_scenario_node_payload and list_modules vs list_operations still require careful reading, creating mild ambiguity.

Nearly all tools follow a snake_case verb_object pattern such as generate_image, list_operations, and search_docs, making the set predictable. capability_map stands out as a noun-style entry point, and import_image_from_url adds a preposition, so it is not perfectly uniform.

Sixteen tools is just above the typical 3-15 well-scoped range, but the count is defensible given the server's dual role: Admin API discovery, schema lookup, validation, execution, recipes, docs, and image generation. Each tool earns its place, though the set is slightly heavy.

The surface covers the full workflow well: orient via capability_map, discover modules and operations, fetch schemas, validate tricky payloads, execute through invoke_operation, and handle image generation/import/regeneration. Minor gaps exist—no dedicated image listing/deletion or quiz-item payload dry-run—but generic invoke_operation can likely cover most API-level needs.