The server defines 2 tools with explicit schemas and descriptions. Both tools have reasonable descriptions (100+ characters) and documented input schemas. However, there are significant gaps: (1) quarto_render accepts complex parameters (format_options as additionalProperties: true) with minimal guidance on valid keys; (2) output schemas are not documented, what does quarto_render return? Is it a file path, structured metadata, or raw bytes?; (3) error handling is absent, no guidance on what happens when render fails, how to retry, or what invalid inputs look like; (4) template parameter documentation mentions HTTP/HTTPS URL support but provides no format constraints or validation hints; (5) the template parameter description is verbose (token-wasteful) and mixes discovery info into a parameter description rather than a separate tool; (6) quarto_list_formats has zero parameter documentation (though it takes no params, the description could clarify what 'formats' means in the context of Quarto vs Pandoc); (7) no tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite quarto_render being a write operation.

• Document the output schema for quarto_render: e.g., '{"status": "success", "output_file": "/path/to/file.pptx", "size_bytes": 12345, "render_time_ms": 2300}' or, if returning raw file bytes, document that clearly.
• Replace additionalProperties: true in format_options with an explicit enum or schema. Document which Quarto YAML options are supported. Provide 2-3 examples in the parameter description.
• Add destructiveHint and idempotentHint annotations to quarto_render in the tool definition (MCP 2024+ spec).
• Shorten the template parameter description and move template discovery to a separate quarto_list_templates tool.
• Add to quarto_render description: 'Renders Quarto Markdown to the specified format. Supports custom PowerPoint templates. Returns the path to the generated file. If Quarto is not installed on the server, returns an error with instructions to install.'
• Add format constraint to output_filename: minLength 1, pattern to block absolute paths and directory traversal (e.g., '^[^/\\]+\.[a-z]+$').
• Document what happens on collision: 'If output_filename already exists, it will be overwritten.'
• Expand quarto_list_formats description to explain it is a discovery tool and document its return type (array of format ID strings).
• Add error handling examples to quarto_render: what errors can occur, and what should the LLM do? (e.g., 'If status is "quarto_not_found", suggest installing Quarto. If status is "invalid_format_options", suggest reviewing the Quarto documentation.')

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry