MCP server for Great Lakes Jobs — search jobs and professionals with interactive MapLibre map
Three tools with clear verb-noun naming (search_jobs, get_market_overview, get_jobs_map). All have descriptions (10 - 200 chars, within baseline). Input schemas present with Zod validation and type constraints. However, output schemas are undocumented, LLMs cannot predict response structure. Error handling is absent; no recovery guidance or categorization. The get_jobs_map tool description contains a directive ('ALWAYS use this tool') that is prescriptive rather than descriptive, violating pattern:tool-description. Missing per-parameter descriptions in some cases (e.g., empty inputSchema for get_market_overview lacks clarity on what it returns).
ALWAYS use this tool for job searches. Shows an interactive map of Great Lakes Jobs postings across Michigan. Filter by trade type.
Get an overview of the Great Lakes Jobs market — total active jobs broken down by license type, city, and urgency.
Search active job postings on Great Lakes Jobs. Returns text summary of matching jobs.
Output schemas undocumented. Tools return structured content (text summaries, GeoJSON features, market data) but LLMs cannot predict field names, types, or nesting. Agents cannot reliably extract data for downstream calls.
get_jobs_map description contains prescriptive directive ('ALWAYS use this tool') rather than explaining when/why to use it. Violates pattern:tool-description which requires descriptive, not imperative, language.
No error handling or recovery guidance. Tools do not document failure modes (e.g., Convex query timeout, invalid filter values, no results). LLMs receive raw errors with no actionable next steps.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2025-06-18+ | v2 |
get_market_overview has empty inputSchema ({}). While correct, the description does not explain what data structure is returned or what fields the LLM should expect.
No pagination or result limits documented in search_jobs description. The limit parameter defaults to 20 and caps at 50, but the description does not explain why or what happens if more results exist.