Mesh

Resolve Term

resolve_term

Read-onlyIdempotent

Map a free-text term or everyday synonym to its canonical MeSH descriptor(s) — the preferred heading to use when searching PubMed. Tries an exact descriptor match first; if none, falls back to a fuzzy contains match (flagged fuzzy). Keyless.

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": {
      "text": "aspirin"
    },
    "name": "resolve_term"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	A term or synonym to canonicalize, e.g. "aspirin", "high blood pressure", "diabetes".
`limit`	No	Max matches (default 10, max 25).

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedJul 29, 2026

addedInput schema / examples

Added value: +[
+  {
+    "text": "aspirin"
+  },
+  {
+    "limit": 15,
+    "text": "high blood pressure"
+  }
+]

First observedJun 11, 2026

TDQS

A4.4/5.0

Behavior4/5

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

The description adds valuable behavioral details beyond annotations, such as the two-step matching strategy (exact then fuzzy) and the fact that it is keyless, without contradicting the read-only and idempotent hints.

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?

The description is extremely concise, with two sentences: the first defines the purpose and the second explains the matching algorithm. No redundant information.

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?

The description covers the core behavior and usage, but lacks details on the return format (no output schema). However, given the simple mapping function and existing schema/annotations, it is mostly complete.

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 schema already covers both parameters with descriptions, but the description adds algorithmic context (exact then fuzzy fallback) that enhances understanding, though not necessary for parameter usage.

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 clearly states the tool maps free-text terms to canonical MeSH descriptors, distinguishing it from siblings like resolve_entity and get_descriptor by specifying the resource and verb.

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?

The description explains when to use the tool (mapping synonyms to PubMed headings) and its matching behavior, but does not explicitly mention when not to use it or contrast with alternatives like search_descriptors.

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

All Mesh tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.