Skip to main content
Glama

search_nerve_lit

Doorzoek de peripheral-nerve-surgery literatuurdatabank semantisch.

Instructions

Doorzoek de peripheral-nerve-surgery literatuurdatabank semantisch.

Args:
    query: de vraag in natuurlijke taal, bv. "supercharged end-to-side AIN naar ulnaris".
    k: aantal passages om terug te geven (default 8).
    year_from: enkel artikels vanaf dit publicatiejaar.
    year_to: enkel artikels tot en met dit publicatiejaar.
    full_text_only: alleen passages uit volledige artikels, niet uit abstracts.

Returns:
    De relevantste passages met hun citaat (titel, tijdschrift, jaar, PMID, DOI).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_nerve_lit"
  }
}

Input Schema

NameRequiredDescriptionDefault
kNo
queryYes
year_toNo
year_fromNo
full_text_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does a reasonable job: it discloses that matching is semantic rather than keyword, that results are passages, that full_text_only excludes abstract-only passages, and that year_to is inclusive. It omits operational traits such as result limits beyond k, corpus scope, or error behavior, which keeps it below a 5.

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

Conciseness4/5

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

Front-loaded one-line purpose followed by a compact Args/Returns block that maps cleanly to the schema; nothing is buried. Minor redundancy: defaults for k and full_text_only restate the schema, though the surrounding semantics still earn the space.

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

Completeness5/5

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

All five parameters are explained, behavior of the filters is spelled out, and the return content (passages plus citation metadata: title, journal, year, PMID, DOI) is described even though an output schema already exists. For a single-purpose search tool this leaves nothing an agent needs for correct invocation.

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

Parameters5/5

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

Schema description coverage is 0%, and the description compensates for every parameter: query is defined as a natural-language question with a worked example, k as the number of passages returned, year_from/year_to with an explicit inclusive upper bound, and full_text_only as excluding abstract-only passages. This adds real meaning the flat schema does not convey.

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: semantic search over a peripheral-nerve-surgery literature database. The word 'semantisch' signals it is a relevance-ranked retrieval tool, which separates it from fetching a single record (get_nerve_lit_article) or aggregate numbers (get_nerve_lit_stats), though it never names those siblings explicitly.

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?

The example query ('supercharged end-to-side AIN naar ulnaris') implies the natural-language phrasing expected, and the year/full-text filters hint at narrowing use cases. There is no explicit when-to-use/when-not-to-use guidance and no routing statement toward the sibling tools, so the agent must infer when this is the right pick.

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