Unified MCP server for Glyphs handbook, API documentation, vocabulary translations, plugins, scripts, SDK guides, news, and Light Table API queries
The server has 3 tools with reasonable naming conventions that follow verb_noun patterns (search_, get_, list_). However, there are significant gaps in parameter descriptions, schema completeness, and output documentation. Tool descriptions are present but brief (40-60 chars), falling below the ideal 50-200 char range for LLM optimization. Most critically, no output schemas are documented, making it impossible for LLMs to understand what fields to expect from each tool. Parameter descriptions are minimal or missing entirely for most inputs. The server lacks error handling guidance, recovery paths, and any security/permission documentation.
[API] Glyphs Python/Objective-C API reference with 16 actions including search_python, get_class, get_member, search_objc, get_header, list_protocols, get_protocol, convert_objc, convert_python, identify_method, search_plugin_api, get_plugin_method, get_plugins_inheriting, find_relationships, search_vanilla_ui, get_vanilla_ui
Generate code template for a specific plugin type
Get plugin class inheritance hierarchy information
Get detailed information about a specific plugin method across all plugins
Get detailed information about a specific plugin type including methods and usage
Read complete vanilla UI component information from local source
[HANDBOOK] Glyphs Handbook operations with actions: search (query, search_scope, max_results), get (filename), toc (chapter), children (chapter), parameter (name), list_parameters, cache (operation: info|update, force)
No output schemas documented for any tool. LLMs cannot determine what fields to expect in responses, breaking downstream tool chaining and field extraction.
Parameter 'ui_item' (get_vanilla_ui) lacks description. The description is present but missing type hints or valid value constraints. Should document: expected format, whether it's case-sensitive, what happens if the component doesn't exist.
Tool descriptions are too brief (35-50 chars). Ideal range is 50-200 chars. 'Search local vanilla UI components (fully local search)' and 'List all available vanilla UI components' lack context on WHEN to use these tools or what they return. LLMs cannot perform proper tool selection with minimal descriptions.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | F | 14 | <=2025-11-25 | v2 |
| 2026-03-09 | F | 35 | - | v1 |
[LIGHTTABLE] Light Table API reference with actions: search (query, max_results), get (api_name), list (category), categories
List all available plugin types with their descriptions
List all available vanilla UI components
[NEWS] Glyphs news and updates with actions: latest (limit), search (query, max_results), category (category), trending, archive (year)
[PLUGINS] Glyphs plugins information with actions: search (query, type), details (plugin_name), method_details (method_name), generate_code (plugin_type, name), list_available, inheritance_info
[SCRIPTS] Glyphs mekkablue scripts reference with actions: search (query, max_results), get (script_name), list (category), categories, trending
[SDK] Glyphs SDK guides and samples with actions: search (query, max_results), guide (filename), list (category), categories, sample (filename)
Search for Glyphs.app plugins by name, type, or functionality
Search local vanilla UI components (fully local search)
[VOCABULARY] Glyphs UI terminology translation with actions: translate (term, target), search (term, locale), mapping (term, source_locale, target_locales), categories
Parameter 'max_results' in search_vanilla_ui has a default of 5 but no minimum/maximum bounds documented. Should specify: range (1-100?), why 5 is the default, what happens if a user passes 1000.
No error handling or recovery guidance. If get_vanilla_ui('NonExistent') fails, the tool provides no guidance on what to do next. Should return: 'Component not found. Call list_vanilla_ui() to see available components.'
No pagination support documented for list_vanilla_ui(). If there are hundreds of components, returning all at once could exhaust context. Should support limit and offset parameters and return total_count.