Skip to main content
Glama

search_openi_images

Search biomedical images such as X-rays, CT scans, and clinical photos. Returns image URLs and source citations.

Instructions

Search Open-i (NLM) for medical, clinical, graphical and dental images.

Open-i (https://openi.nlm.nih.gov) is the U.S. National Library of Medicine's open-access biomedical image search engine. It indexes figures, charts, X-rays, photographs and illustrations from PubMed Central articles and other collections. No API key is required.

┌──────────────────────────────────────────────────────────────────────┐ │ ⚠️ TRANSLATION RULE — READ THIS BEFORE CALLING THE TOOL │ │ │ │ The Open-i index is ENGLISH-ONLY. You (the LLM agent) MUST translate │ │ every Portuguese term the user gives you into English BEFORE putting │ │ it into query. Never send Portuguese to the API. │ │ │ │ "incisão oral" -> "oral incision" │ │ "odontolegista" -> "forensic dentistry" │ │ "anatomia dental" -> "dental anatomy" │ │ "radiografia panorâmica"-> "panoramic radiograph" │ │ "cárie" -> "dental caries" │ │ │ │ If the user writes in English already, pass it through unchanged. │ └──────────────────────────────────────────────────────────────────────┘

Args: query: The search terms, IN ENGLISH (translate first — see rule above). m: Start index of the result window (1-based). Default 1. n: End index of the result window. Default 10. Ask for a small window (e.g. m=1, n=10) unless the user wants more. it: Image Type filter. One or more comma-separated codes from [xg, xm, x, u, ph, p, mc, m, g, c]. Most useful: g = graphics / charts / diagrams / illustrations ph = photograph (clinical / gross photo) x = X-ray xm = mammography xg = angiography u = ultrasound c = CT m = MRI mc = microscopy / histology p = PET Leave empty to search all image types. sp: Specialties filter. Comma-separated codes, e.g. "d" for dentistry. Full set: [b, bc, c, ca, cc, d, de, dt, e, en, f, eh, g, ge, gr, gy, h, i, id, im, n, ne, nu, o, or, ot, p, py, pu, r, s, t, u, v, vil]. Leave empty for all specialties. at: Article Type filter. Comma-separated codes from [ab, bk, bf, cr, dp, di, ed, ib, in, lt, mr, ma, ne, ob, pr, or, re, ra, rw, sr, rr, os, hs, ot]. Leave empty for all article types.

Returns: A dict with keys: query - the (English) query that was actually sent total - total number of matches Open-i reports returned - how many results are in this response api_url - the exact URL that was requested (for transparency) results - a clean list; each item has: title, image_url, thumbnail_url, summary, article_url, uid

To show a result to the user, render the image with Markdown:
    ![title](image_url)
and cite the source with [Source](article_url).

On failure the dict instead has:
  error    - a human-readable message
  status   - the HTTP status code if the API responded (400/500/…)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mNo
nNo
atNo
itNo
spNo
queryYes
Behavior5/5

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

No annotations provided, so description carries full burden. It discloses no API key required, English-only index, translation requirement, result structure, error format, pagination parameters, filter options, and rendering guidance. Does not mention rate limits or destructive actions (irrelevant for search). Comprehensive.

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?

Description is lengthy but well-structured: brief intro, prominent translation rule box, parameter list, return format. Each section earns its place. Slight verbosity but organized for clarity.

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?

Fully describes return value (dict with keys) and error handling. Covers filtering options (image type, specialty, article type). Includes rendering instructions. No output schema, but complete for a search tool. Only missing comparison to sibling 'openi_reference', but not critical.

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

Parameters5/5

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

Schema has 0% description coverage; description compensates fully. Each parameter (query, m, n, it, sp, at) is explained with defaults, usage hints, and code lists. Adds critical translation rule for 'query' and practical advice for 'n'.

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 it searches Open-i for medical images, specifying resource (Open-i/NLM), verb (search), and scope (medical, clinical, graphical, dental). The sibling 'openi_reference' suggests different functionality, so this tool's purpose is distinct.

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

Usage Guidelines5/5

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

Provides explicit translation rule: translate Portuguese to English before querying. Recommends small result windows. Implicitly guides when not to use (if query is in Portuguese without translation). No direct comparison to sibling, but clear boundaries.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/LeviReisJs/mcp-openi-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server