This repository is a monorepo containing multiple plugins/skills, but only 2 tools are claimed and neither has visible MCP registration, schemas, or descriptions in the provided source code. The arxiv-latex-display-math-extractor and latex-math-validity-oracle are Rust binaries with Cargo.toml files showing dependencies (pulldown-latex, serde, serde_json) but NO tool registration code, NO parameter schemas, and NO descriptions beyond the brief claims in the evaluation prompt. The Makefile and package.json files show this is a collection of unrelated utilities (FloatingClock macOS app, calcom-commander, claude-tts-companion, etc.), not a cohesive MCP server. Without visible MCP server implementation (no MCP tool definitions, no input/output schemas, no parameter descriptions), this cannot be scored as a working MCP server.

• Locate or create the actual MCP server implementation. If this monorepo contains MCP servers, they must be registered with proper tool definitions (name, description, inputSchema, outputSchema). The provided Cargo.toml and Makefile snippets show only standalone CLI tools, not MCP tool registrations.
• For each tool, define a complete JSON Schema for inputs. Include type declarations for every parameter, required/optional flags, enums for constrained values, and min/max for numeric ranges.
• Write a description for each tool (10 - 1024 characters) explaining what it does, when to use it, and what it returns. Example: 'Extracts display-mode LaTeX equations from arXiv papers. Returns JSON array of {equation, line_number, confidence} objects. Call this before validate_latex_math to identify equations that need validation.'
• Add descriptions to every input parameter. Example for a 'paper_id' param: 'arXiv paper ID (format: YYMM.NNNNN, e.g., 2301.12345). Used to fetch and parse the paper.'
• Rename tools to follow verb_noun convention: arxiv-latex-display-math-extractor → extract_arxiv_display_math; latex-math-validity-oracle → validate_latex_math.
• Document the output schema as a JSON object with typed fields. Example: '{equations: [{equation: string, line_number: integer, confidence: number}], total_count: integer}'.
• Add error handling: categorize failures as retryable (network timeout, rate limit) vs. user-fixable (invalid paper ID format, unsupported LaTeX dialect) vs. fatal. Return actionable messages: 'Invalid arXiv ID format, expected YYMM.NNNNN, got "2024-01". Try again with correct format or search for the paper first.'