@mcp/openverse
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_imagesC | Search for openly-licensed images on Openverse |
| get_image_detailsC | Get detailed information about a specific image |
| get_related_imagesC | Get images related to a specific image |
| get_image_statsB | Get statistics about image providers and counts |
| search_images_for_essayC | Search for images suitable for illustrating an essay |
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 5 tools
Most tools have distinct purposes: get_image_details, get_image_stats, get_related_images, and search_images are clearly differentiated. However, search_images and search_images_for_essay have overlapping functionality, as the latter seems like a specialized version of the former, which could cause minor confusion for an agent.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., get_image_details, search_images). There are no deviations in naming conventions, making the set predictable and easy to parse.
With 5 tools, the count is well-scoped for an image search and retrieval server. Each tool serves a specific function in the domain, and there are no extraneous or redundant tools, making the set appropriately sized.
The tool surface covers core operations for image search and retrieval, including search, details, stats, and related images. A minor gap exists in lacking explicit tools for actions like filtering or advanced search parameters, but agents can likely work around this using the provided search tools.