This server has severe definition quality issues. Both tools have descriptions in Chinese with low information density and minimal parameter documentation. The parse_and_extract tool has a convoluted description that reads as internal implementation notes rather than a clear agent-facing specification. Input schemas exist but lack proper type annotations and descriptions for parameters. Output schemas are completely undocumented, callers cannot anticipate return structure. No error handling guidance is provided. The list_supported_frameworks tool has a minimal description and no parameters. Neither tool follows the naming or documentation patterns required for production-grade agent tooling.

• Rewrite tool descriptions in English, focusing on WHAT the tool does and WHEN to call it, not on implementation logic. E.g., 'parse_and_extract: Extracts component source code (HTML, CSS, JavaScript) from a Uiverse.io component URL. Supports frameworks: HTML, React, Vue, Svelte, Lit. Input format: "FRAMEWORK URL" (e.g., "React https://uiverse.io/user/component-name"). Use this to fetch ready-to-use component code.'
• Add enum schema constraint to 'query' parameter documenting supported frameworks, or split into separate tools per framework (extract_html_component, extract_react_component, etc.) to avoid hallucination.
• Document return schemas explicitly. E.g., 'parse_and_extract returns a markdown code block string containing the extracted component code. list_supported_frameworks returns a markdown-formatted list of supported framework names.'
• Add error handling guidance to parse_and_extract description: 'If the URL is invalid or not from uiverse.io, this tool will return an error. Ensure the URL is in the format https://uiverse.io/username/component-name. If you only have a component name, ask the user for the full URL.'
• Remove example values from descriptions. Instead, declare a regex pattern in the input schema for URL validation, and declare an enum ['HTML', 'React', 'Vue', 'Svelte', 'Lit'] for framework validation.
• Rename parse_and_extract to extract_uiverse_code or similar to clarify the action. The 'and' signals multiple responsibilities, if parsing and extraction must happen together, that's fine, but rename to reflect the primary user intent.