This is a conformance test fixture server with 13 tools designed to validate MCP protocol compliance. All tools have descriptions and input schemas are visible. However, most tools have empty or minimal input schemas ({}), and descriptions, while present, are terse and conformance-focused rather than LLM-optimized. Tool names follow verb_noun convention (test_*). No parameter descriptions exist for the two tools with non-empty inputs (test_sampling, test_elicitation). Error handling is basic. The server demonstrates protocol features (logging, progress, sampling, elicitation, tool annotations) but prioritizes conformance testing over production-grade tool design.

• Add parameter descriptions to test_sampling and test_elicitation. E.g., 'prompt: The text to send to the client's LLM for completion sampling (string, required)'.
• Expand tool descriptions to 80-150 characters, explaining WHAT the tool does, WHEN to use it, and what it returns. E.g., 'test_sampling: Requests the client to sample a completion from its LLM using the provided prompt. Returns the sampled text. Use to test server-initiated sampling capability.'
• Document output schemas for all tools. Even conformance fixtures should specify return types (e.g., 'Returns: {text: string}' for test_simple_text).
• Rename json_schema_2020_12_tool to validate_json_schema_2020_12 or test_json_schema_2020_12_validation to follow verb_noun convention.
• Add non-empty input schemas to tools with empty {} inputs. At minimum, document that no parameters are required (e.g., 'Input: {} (no parameters required)').

Inferred effective spec: 2026-07-28+.

• Relies on Sampling (deprecated) - integrate directly with the LLM provider API