Search Nobel Prize data by award year and category to find relevant prize records and filter results by limit.
Search Nobel Prize data by year and/or category.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No | Award year (e.g. 2023). | |
| limit | No | Max results (default 10). | |
| category | No | Category code: che, eco, lit, pea, phy, med. |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not state read-only behavior, pagination/limit semantics, authentication needs, or return shape; only the search action is named.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no wasted words. It is appropriately sized for a simple search tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool with a fully described schema, the core callable purpose is present. However, it does not clarify return shape or how it differs from nobel_laureates, leaving notable gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, and all three parameters have clear schema descriptions. The description mentions year and category but omits limit, so it adds little beyond the schema; baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'Search' and resource 'Nobel Prize data', and names the year/category filter dimensions. However, it does not distinguish this tool from the sibling nobel_laureates, so sibling differentiation is absent.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The phrase 'by year and/or category' implies filtering usage, but there is no explicit when-to-use, when-not-to-use, or alternative such as nobel_laureates. Usage is only weakly implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.