Skip to main content
Glama

NLM MeSH descriptor for an exact heading: MeSH ID, label

health_mesh_biomedical_thesaurus
Read-only

NLM MeSH (Medical Subject Headings) descriptor for an exact heading: MeSH ID, label, entry terms (synonyms) and allowable subheadings (qualifiers). Exact match only; no scope notes (the public lookup API does not return them). Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "heading": "<heading>"
    },
    "name": "health_mesh_biomedical_thesaurus"
  }
}

Input Schema

NameRequiredDescriptionDefault
headingYesExact MeSH heading, letters, digits, spaces, commas, hyphens and parentheses, 2 to 100 characters

Output Schema

NameRequiredDescriptionDefault
sourceNo
headingNo
checkedAtNo
entryTermsNo
descriptorIdNo
allowableQualifiersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses several behavioral traits an agent could not otherwise infer: per-call pricing ($0.002), the x402/USDC payment mechanism, the fact that failed calls are not billed, and a hard data limitation (no scope notes). This is exactly the kind of cost and capability boundary information annotations cannot carry, and it does not conflict with readOnlyHint=true.

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 compact sentences, front-loaded with what is returned before moving to constraints and cost. Every clause carries distinct information — match strictness, missing scope notes, price, payment rail, failure billing — with no restatement of the name or title.

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?

For a one-parameter lookup with an output schema and readOnly annotations, the description covers everything left open: exactness of matching, known data gaps, and the paid-call cost model that affects whether an agent should call it. Nothing essential to correct invocation is missing.

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 single parameter is already fully documented in the schema (allowed characters, 2-100 length), which sets the baseline at 3. The description adds real meaning on top by stating the match must be exact rather than partial, sharpening how an agent should construct the value.

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

Purpose5/5

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

The description names the resource precisely (NLM MeSH descriptor), the input constraint (an exact heading), and the payload an agent gets back (MeSH ID, label, entry terms, allowable subheadings). The phrase 'Exact match only' also stakes out scope against any fuzzy-search interpretation, so an agent can tell what this tool will and will not resolve.

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

Usage Guidelines4/5

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

It gives clear selection context: use it when you have an exact heading, and be aware it cannot supply scope notes because the public API does not return them. It does not explicitly name an alternative for near-match or text-search lookups, so the 'when not to use' side is only implied by the exact-match constraint.

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.

Resources