Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

search_biomedical_images

Retrieve biomedical images from Open-i and Europe PMC. Filter by image type, collection, license, or specialty to find clinical photos, X-rays, microscopy, and more with captions and article metadata.

Instructions

πŸ–ΌοΈ Search biomedical images across Open-i and Europe PMC.

Searches medical/scientific images from multiple sources and returns image URLs with metadata (caption, article info, MeSH terms).

═══════════════════════════════════════════════════════════════ ⚠️ CRITICAL - LANGUAGE REQUIREMENT: ═══════════════════════════════════════════════════════════ Open-i ONLY supports English queries. If the user queries in non-English (Chinese, Japanese, Korean, etc.), you MUST:

  1. Translate the query to English medical terminology first

  2. Then call this tool with the English query Example: "ε–‰ι ­ζ°΄θ…«" β†’ "laryngeal edema" "胸部Xε…‰θ‚Ίη‚Ž" β†’ "chest X-ray pneumonia"

The tool has built-in translation hints for common CJK medical terms, but YOU should always verify the translation is correct.

═══════════════════════════════════════════════════════════ SOURCES: ═══════════════════════════════════════════════════════════════

  • Open-i (NLM): X-ray, microscopy, clinical images (~133K)

  • Europe PMC: Figure captions from 33M+ articles (future)

═══════════════════════════════════════════════════════════════ EXAMPLES: ═══════════════════════════════════════════════════════════════

General image search: search_biomedical_images("chest pneumonia CT scan")

X-ray only: search_biomedical_images("fracture", image_type="x")

Microscopy images: search_biomedical_images("histology liver", image_type="mc")

Clinical teaching images (MedPix): search_biomedical_images("pneumothorax", collection="mpx")

Case reports with CC-BY license, sorted by date: search_biomedical_images( "lung cancer", article_type="cr", license_type="by", sort_by="d" )

Cardiology specialty images: search_biomedical_images("echocardiogram", specialty="c")

Video content only: search_biomedical_images("surgery technique", video_only=True)

═══════════════════════════════════════════════════════════════

Args: query: Search query (e.g., "chest X-ray pneumonia") sources: Image sources to search: - "auto": Select best sources (default) - "openi": Open-i only (best for medical images) - "europe_pmc": Europe PMC only (future) - "all": Search all sources image_type: Filter by image type (Open-i only): Positive filters: - "c": CT scan images - "g": Graphics / line art / diagrams - "m": MRI images - "mc": Microscopy / histology images - "p": PET scan images - "ph": Photographs / clinical photos - "u": Ultrasound images - "x": X-ray images Exclusion filters: - "xg": Exclude Graphics (removes graphic images from results) - "xm": Exclude Multipanel (removes multipanel images) - None: All types (default) collection: Filter by collection (Open-i only): - "pmc": PubMed Central articles - "mpx": MedPix clinical teaching images (high quality) - "cxr": Chest X-ray collection - "hmd": History of Medicine - "usc": USC collection - None: All collections (default) open_access_only: Only return open access images (default True) limit: Maximum number of images to return (default 10, max 50) sort_by: Sort results by (Open-i only): - "r": Relevance (default) - "d": Date (newest first) - "o": Oldest first - "t": Title - "e": Education relevance - "g": Graphics priority article_type: Filter by article type (Open-i only): - "cr": Case Report - "or": Original Research - "re": Review - "sr": Systematic Review - "ra": Research Article - "ed": Editorial - "lt": Letter - "bk": Book - and more... (see API docs) specialty: Filter by medical specialty (Open-i only): - "r": Radiology - "c": Cardiology - "ne": Neurology - "pu": Pulmonology - "d": Dermatology - "g": Gastroenterology - "or": Orthopedics - "o": Ophthalmology - "s": Surgery - "p": Pediatrics - "id": Infectious Disease - "i": Immunology - and more... (see API docs) license_type: Filter by Creative Commons license (Open-i only): - "by": CC-BY (Attribution) - "bync": CC-BY-NC (Attribution-NonCommercial) - "byncnd": CC-BY-NC-ND (Attribution-NonCommercial-NoDerivs) - "byncsa": CC-BY-NC-SA (Attribution-NonCommercial-ShareAlike) subset: Filter by subject subset (Open-i only): - "b": Behavioral Sciences - "c": Cancer - "e": Ethics - "s": Surgery - "x": Toxicology search_fields: Search in specific fields (Open-i only): - "t": Title only - "m": MeSH terms only - "ab": Abstract only - "msh": MeSH heading only - "c": Caption only - "a": Author only video_only: If True, only return video content (default False)

Returns: Formatted image results with URLs, captions, and article metadata

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
sourcesNoauto
image_typeNo
collectionNo
open_access_onlyNo
limitNo
sort_byNo
article_typeNo
specialtyNo
license_typeNo
subsetNo
search_fieldsNo
video_onlyNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries full burden. It thoroughly discloses sources (Open-i, Europe PMC), language limitation, filtering capabilities, example calls, and return format. This transparency exceeds expectations.

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?

The description is long but well-structured with clear sections (purpose, critical warning, sources, examples, args). It earns its length given the tool complexity, but could be slightly more concise.

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?

Given 13 parameters, 1 required, and an output schema, the description covers all necessary aspects: all parameters with values, language constraint, sources, examples, and return information. It is complete.

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 description coverage is 0%, so the description must compensate. It does so by exhaustively listing each parameter's possible values, meanings, and defaults with examples. This adds immense value beyond the raw schema.

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 biomedical images across Open-i and Europe PMC, returning image URLs with metadata. This distinguishes it from sibling tools like search_gene or search_compound, which are for other data types.

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 provides detailed usage guidance including explicit language requirements, parameter options, and examples. However, it does not explicitly state when not to use this tool or suggest alternative siblings, leaving some room for improvement.

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/u9401066/pubmed-search-mcp'

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