MCP server for Swiss intellectual property data (trademarks, patents, SPC) via the IGE/IPI Swissreg API
Four search tools with consistent schemas and basic descriptions. All tools have proper input schemas with required parameters and pagination support. Descriptions are present but generic (avg ~80 chars, below the 194-char baseline). Parameter descriptions are minimal. No output schemas documented. Error handling and recovery guidance absent. Tool names follow verb_noun pattern (search_*) but lack specificity about what distinguishes each search type. No tool annotations visible in definitions despite toolAnnotations=true in features.
Search for Swiss patent publications by various criteria
Search for Swiss patents by various criteria (number, applicant, status, etc.)
Search for Swiss Supplementary Protection Certificates (SPC/ESZ) by various criteria
Search for Swiss trademarks by various criteria (name, owner, status, etc.)
Output schemas not documented. LLMs cannot plan downstream operations or extract required fields without knowing response structure.
Parameter descriptions are minimal. 'Search query' and 'Pagination token' lack actionable detail about format, constraints, or examples. LLMs cannot infer valid input ranges.
Tool descriptions are generic and under 100 chars. They do not explain WHEN to use each tool vs. the others, or what distinguishes trademark search from patent search in practice.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |
No error handling or recovery guidance. If a search returns no results or hits a rate limit, the LLM has no guidance on what to do next.
page_size parameter lacks min/max constraints. Unbounded integers could cause API overload or timeout. No guidance on default or recommended values.