MCP server for searching Korean space, aerospace, and defense R&D support programs and UK public tenders with company matching and relevance classification
Server has 9 tools with complete schemas and descriptions. Naming follows verb_noun convention (search_, get_, match_, list_, classify_). Descriptions are present (avg ~120 chars) but lack LLM-optimized guidance on WHEN to use each tool vs alternatives. Parameter schemas are well-typed with enums where appropriate (spaceCategory, status, applicantType). Critical gap: no output schemas documented, LLMs cannot plan downstream calls or extract structured data. Error handling and recovery guidance absent. match_* tools accept complex nested objects but lack dependency documentation. search_space_programs has redundant camelCase/snake_case parameter pairs (spaceCategory/space_category, sourceFamily/source_family, etc.) creating confusion.
Classify raw Korean public-notice text into core space, satellite, launch, space data, defense space, aerospace, or adjacent categories.
Return the latest Korea Space Support ingestion report, including generated counts and excluded candidates with reasons.
Get detailed source-linked information for a Korean space program by ID, including full eligibility, security requirements, and attachment URLs.
Get full details for a tender by ID, including source URL and last checked timestamp.
List Korea Space Support MCP source families with MVP status, collection policy, and known gaps.
Rank Korean space programs against a company/research profile with explainable fit scores, missing qualifications, and partnership requirements.
No output schemas documented for any tool. LLMs cannot infer response structure, plan chaining, or extract required fields for downstream calls.
search_space_programs has redundant parameter pairs (spaceCategory/space_category, sourceFamily/source_family, etc.). Creates ambiguity, LLMs may pass both, causing undefined behavior.
match_tenders_to_company and match_space_programs_to_company accept complex nested companyProfile objects but lack documentation of required vs optional fields, dependencies, or validation rules.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
Rank tenders against a company profile with explainable fit scores, risks, and missing information.
Search Korean space, aerospace, defense-space, astronomy, satellite, launch, UAM, and space-adjacent support/R&D program samples.
Search Contracts Finder-first UK public tender sample data by query, region, CPV, value, and deadline.
No error handling or recovery guidance. Tools lack descriptions of failure modes, retryability, or what the LLM should do if a call fails (e.g., 'Try search_tenders() with a broader query').
Descriptions lack WHEN-to-use guidance. E.g., search_tenders vs match_tenders_to_company both search, but the distinction is unclear. LLMs may pick the wrong tool.