Skip to main content
Glama

NS Pros MCP Gateway

nobel__get_prizes_by_year

Get all Nobel Prizes awarded in a specific year, optionally filtered by category (e.g., "Chemistry", "Peace"). Returns laureate names, categories, and citations.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "year": 2023
    },
    "name": "nobel__get_prizes_by_year"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearYesYear to look up (e.g., 2023). Must be 1901 or later.
categoryNoNobel Prize category: phy (Physics), che (Chemistry), med (Medicine), lit (Literature), pea (Peace), eco (Economics)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full behavioral burden; 'Get' implies a read-only lookup and it usefully lists the returned fields (laureate names, categories, citations). It omits what happens for years with no awards or when a category had no laureate, and does not restate the 1901 floor that the schema enforces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, zero waste, with the core action and the optional filter front-loaded and the return shape appended last. Nothing is repeated or padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter read lookup with no output schema, the description covers the action, the filter, and the returned fields — enough to call it correctly. The only gap is the mismatched category examples, which is a correctness issue rather than an omission.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already defines both parameters. The description actively conflicts with it on the category parameter: it gives example values 'Chemistry' and 'Peace' while the schema requires the codes 'che' and 'pea', which could lead an agent to send an invalid value. That is a real risk rather than neutral redundancy.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource ('Get all Nobel Prizes awarded in a specific year') plus the optional category filter, so the agent knows exactly what the tool returns. It does not need to differentiate from the listed siblings, which are unrelated research/market tools, but it never explicitly states that scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the year-scoped framing ('a specific year'), but there is no explicit when-to-use guidance, no statement about when to omit the category parameter, and no alternatives named. An agent can infer correct usage but gets no routing help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.