Server has 5 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-50 chars, mostly short), and input schemas are present with type definitions. However, parameter descriptions are sparse or missing entirely. The submit_job tool has a complex nested object schema but lacks guidance on dependencies between fields. No output schemas are documented. Error handling is minimal, tools raise exceptions without recovery guidance. Tool names follow verb_noun convention (get_*, download_*, submit_*) which is good, but descriptions lack context on when to use each tool vs. alternatives.
Download finished job using job id.
Get the ids of all collections available in the catalogue.
Get more details for a specific collection.
Fetch list of jobs.
Submit a download request.
Parameter descriptions missing or trivial. 'status' in get_jobs lacks explanation of what statuses mean or when to filter. 'download_request' in submit_job is a complex nested object with no guidance on required vs. optional fields or field dependencies.
Output schemas not documented. Tools return Response, CollectionInfo, DownloadResponse, and list[str] objects, but LLMs have no visibility into field structure. Agents cannot plan downstream calls or extract required IDs.
Tool descriptions are too short (10-50 chars). 'Fetch list of jobs' and 'Download finished job using job id' lack context on when to use each tool, what prerequisites exist, or what the LLM should do with results.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
No error handling or recovery guidance. Tools raise CdsEnvironmentVariablesNotSetError and generic exceptions without telling the LLM what to do next. No distinction between retryable, user-fixable, and fatal errors.
submit_job has undocumented field dependencies. 'time', 'area', 'data_format', 'download_format' have defaults, but 'pressure_level' is optional with no guidance on when it applies. Complex nested schemas need explicit dependency documentation.