Skip to main content
Glama

Medlineplus

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search

search
Read-onlyIdempotent

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

Input Schema

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

Output Schema

TableJSON 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. Changed1 schema field changed
    • removedInput schema / properties / knowledge_response_type
      Removed value: -{
-  "description": "application/json (default) | application/xml",
-  "type": "string"
-}
  2. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "diabetes"
+  },
+  {
+    "db": "drug",
+    "limit": 20,
+    "query": "aspirin"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "results": {
+      "items": {
+        "properties": {
+          "organization": {
+            "description": "Organization publishing the resource",
+            "type": "string"
+          },
+          "rank": {
+            "description": "Result ranking position",
+            "type": "number"
+          },
+          "snippet": {
+            "description": "Brief excerpt or summary of the result",
+            "type": "string"
+          },
+          "title": {
+            "description": "Title of the result",
+            "type": "string"
+          },
+          "url": {
+            "description": "URL to the MedlinePlus or NLM resource",
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "returned": {
+      "description": "Number of results in this response",
+      "type": "number"
+    },
+    "total": {
+      "description": "Total number of matching results across all pages",
+      "type": "number"
+    }
+  },
+  "required": [
+    "total",
+    "returned",
+    "results"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds the database scope (MedlinePlus/NLM) but does not disclose other behavioral traits such as pagination, result ordering, or potential limitations. This is comparable to a basic read operation with some context, but not rich.

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 a single, concise sentence that is front-loaded with the key verb and object. It is free of redundancy and delivers maximum meaning in minimal space.

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?

Given the tool's simplicity, the presence of an output schema, and comprehensive annotations, the description is largely complete. It conveys the core function and scope, though it omits any usage guidance or mention of default behaviors, which are partially covered by annotations and schema.

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 coverage is 75% with descriptions for 'db', 'limit', and 'retstart'. The description adds minimal parameter context beyond what the schema provides, only implying that 'query' is a free-text search term. This does not significantly enhance schema understanding.

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 clearly states a specific action ('Free-text search') and resource ('MedlinePlus topics (or related NLM databases)'). It is not a tautology and gives enough detail to understand the tool's scope, though it does not explicitly distinguish itself from sibling tools like 'search_within'.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or comparisons to sibling search tools, leaving the agent to infer usage context.

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

All Medlineplus toolsInspect
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.

Resources