An MCP server that exposes JumpServer API endpoints as MCP tools by converting OpenAPI schema to MCP tools
Critical failure: The single tool 'dynamic_jumpserver_api_tools' has NO explicit schema definition visible in source code. Tool names, parameters, and output schemas are dynamically generated from JumpServer's OpenAPI spec at runtime, not statically defined or validated. The description is generic placeholder text ('Tools are dynamically generated...') that does NOT explain what specific tools are available, when to use them, or what they return. No parameter descriptions, no input validation guidance, no error recovery hints. This violates the core principle that tool definitions must be self-documenting for LLM selection and safe execution. Dynamic generation without static schema export makes this unmaintainable and unsafe for production agents.
Tools are dynamically generated from JumpServer OpenAPI schema. All tools converted from OpenAPI endpoints are registered and available for execution. The exact tool names and schemas depend on the OpenAPI specification provided by the JumpServer instance.
No input schema visible for tool. Tool definition is entirely dynamic (generated from OpenAPI at runtime). Cannot verify parameter types, required fields, constraints, or descriptions. Violates pattern:tool requirement for explicit, static schema.
Tool description is generic placeholder (58 chars). Does not explain what tools are available, when to use them, or what they return. LLMs cannot determine tool selection criteria. Violates pattern:tool-description (10-1024 chars, actionable content).
Dynamic tool generation from external OpenAPI spec means tool definitions are not version-controlled, not reviewable, and not testable in CI/CD. Changes to JumpServer API silently change available tools without code review. Violates pattern:tool-registry and code review best practices.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 19 | <=2025-11-25 | v2 |
No error handling guidance visible. Tool execution delegates to _execute_api_tool() but no documentation of failure modes, retryability, or recovery steps. Violates pattern:recovery-guide.
Authorization passed via experimental session_token in request context. No documentation of required permissions, scope declarations, or audit trail. Violates pattern:scope-declaration and pattern:audit-trail.