Skip to main content
Glama

get_nerve_lit_stats

Reports corpus coverage and size statistics for the peripheral nerve surgery literature database, showing how many PubMed records are indexed and whether hits came from full text or abstract.

Instructions

Toon de omvang en toestand van de literatuurdatabank.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about side effects, permissions, rate limits, or whether the call is read-only (only "Toon" weakly implies it). The presence of an output schema covers return values, but the operational profile of the call remains unstated.

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?

A single short sentence with no filler, and the verb leads. It is efficient, though the brevity shades into under-specification rather than tight communication.

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 (no params, output schema present), so most of the burden is light and return values need not be explained. Still, the description never clarifies what "toestand" measures or how the result should be used, which leaves the definition only minimally adequate.

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

Parameters4/5

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

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. No parameter-related claims are made or contradicted.

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

Purpose3/5

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

"Toon de omvang en toestand van de literatuurdatabank" gives a verb (show) and a resource (the literature database), so the broad intent is readable. However, "toestand" (state/condition) is undefined — it is unclear whether it returns counts, health indicators, or coverage metrics — and nothing in the text distinguishes it from the sibling article/search tools beyond a vague notion of "stats".

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no mention of the alternatives (get_nerve_lit_article, search_nerve_lit). An agent must infer that this is a metadata/overview call rather than a content lookup.

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