Skip to main content
Glama

NS Pros MCP Gateway

nobel__search_laureates

Search Nobel Prize laureates by name and/or category (e.g., "Physics", "Medicine", "Literature"). Returns biography, prizes won, and award motivation.

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": {
      "name": "Einstein"
    },
    "name": "nobel__search_laureates"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoFull or partial name of the laureate (e.g., "Einstein", "Marie Curie")
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.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the return payload (biography, prizes won, award motivation), which compensates for the absent output schema. It says nothing about partial-match semantics, result limits, pagination, or whether the two filters combine as AND, so an agent cannot predict result size or matching behavior.

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, front-loaded with purpose and followed by return content, with no filler. Every clause conveys something an agent would otherwise have to guess. The only defect is the misleading category examples, which is a correctness issue rather than a verbosity one.

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

Completeness3/5

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

The tool is simple (two optional parameters, flat schema, no output schema), and the description covers both what goes in and roughly what comes out. It is nonetheless incomplete on matching semantics and result limits, and the category value mismatch undercuts the one parameter detail it does provide.

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?

The schema has 100% description coverage, setting a baseline of 3, but the description's category examples ("Physics", "Medicine", "Literature") conflict with the schema's actual accepted codes (phy, che, med, lit, pea, eco). This actively risks the agent passing a full category name the endpoint may reject, so it subtracts value rather than adding it.

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?

States a specific verb and resource ("Search Nobel Prize laureates") plus the two supported filter axes, so an agent knows exactly what the call does. It does not differentiate itself from neighbours like nobel__get_prizes_by_year or nobel__company_register_search, so it stops short of a 5.

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 only implied: the mention of "by name and/or category" hints at partial-lookup scenarios but gives no explicit when-to-use, when-not-to-use, or alternative tool. An agent must infer that year-based queries belong to nobel__get_prizes_by_year rather than being told.

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.