openi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_openi_imagesA | 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 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 |
| openi_referenceA | Return the Open-i filter code reference (image types, specialties, article types). Handy when you need to look up which filter code corresponds to what, without leaving the conversation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have completely different purposes: one is for looking up filter codes, the other for searching images. There is no overlap or ambiguity.
Both tools follow a consistent 'openi_verb_noun' pattern using snake_case, making them predictable.
With only 2 tools, the server feels thin for a biomedical image search engine. A couple more tools (e.g., fetching image details, listing filters) would be appropriate.
The search tool covers the primary use case, but there is no way to retrieve dynamic filter options or individual image metadata beyond what the search returns, leaving minor gaps.