Skip to main content
Glama

Medlineplus Search

medlineplus_search
Read-onlyIdempotent

Free-text search across MedlinePlus topics (or related NLM databases).

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": {
      "query": "diabetes"
    },
    "name": "medlineplus_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
dbNohealthTopics (default) | healthTopicsSpanish | drug | herb | meshhd | genetic
limitNo1-100 (default 10)
queryYes
retstartNo0-based offset

Output Schema

NameRequiredDescriptionDefault
totalYesTotal number of matching results across all pages
resultsYes
returnedYesNumber of results in this response

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered externally. The description adds that searches can span multiple NLM databases, which is a real behavioral fact not in the annotations. It says nothing about result ordering, pagination behavior, or coverage limits, so it adds only modest value beyond the structured fields.

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 front-loaded sentence with no filler or repetition. It is efficiently sized, though the brevity leaves information gaps that a second short clause about database selection could have closed without bloat.

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?

An output schema exists, so return values need no explanation, and four parameters with 75% schema coverage are largely documented structurally. What is missing is guidance on choosing among the db values (healthTopics vs drug vs meshhd) and on how free-text matching behaves, which matters for a search tool. Adequate but with clear gaps.

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

Parameters3/5

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

Schema description coverage is 75%, so the schema already explains db values, the 1-100 limit range, and the 0-based retstart offset. The description's parenthetical "(or related NLM databases)" reinforces the multi-database nature of the db parameter but adds no syntax or edge-case detail. With high-but-not-complete coverage, the baseline 3 is appropriate.

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?

The description gives a specific verb and resource: "Free-text search across MedlinePlus topics," and adds the parenthetical scope of related NLM databases. An agent immediately knows this is a keyword lookup over a medical reference corpus. It stops short of distinguishing itself from the odd mix of sibling tools, but none of those listed are close substitutes.

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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The only implicit guidance is that queries should be free-text rather than structured. An agent must infer the fit from the one-line scope declaration.

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.