Skip to main content
Glama
AiAgentKarl

Museum MCP Server

by AiAgentKarl

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
tool_search_artworksA

Kunstwerke in Museumssammlungen suchen.

tool_get_artwork_detailsB

Vollstaendige Details zu einem Kunstwerk abrufen.

tool_search_by_artistC

Kunstwerke eines bestimmten Kuenstlers suchen.

tool_get_met_departmentsA

Alle Abteilungen des Metropolitan Museum of Art abrufen.

Returns: Liste aller Departmente mit ID und Name fuer gezielte Suchen

tool_search_by_departmentB

Kunstwerke in einer bestimmten Met-Abteilung suchen.

tool_get_museum_highlightsB

Kuratierte Highlights aus einem Museum abrufen.

tool_get_random_artworkB

Ein zufaelliges Kunstwerk aus einem Museum abrufen.

tool_search_by_periodB

Kunstwerke nach historischer Periode suchen.

tool_compare_museumsC

Einen Suchbegriff in beiden Museen gleichzeitig suchen und Ergebnisse vergleichen.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 9 tools

Disambiguation4/5

The tools are mostly distinct, but `tool_search_artworks` (generic search) and `tool_search_by_artist`, `tool_search_by_department`, and `tool_search_by_period` could be confused, especially if the generic search already supports filtering. However, the focused search tools have clear parameters, so overlap is manageable.

Naming Consistency4/5

Tools follow a consistent `tool_` prefix followed by a verb_noun pattern (e.g., `tool_get_met_departments`, `tool_search_artworks`). There are minor inconsistencies like `tool_compare_museums` (verb_object without underscore) and `tool_get_artwork_details` vs `tool_get_museum_highlights` but overall the pattern is recognizable.

Tool Count5/5

With 9 tools, the server is well-scoped for a museum-focused MCP server. Each tool addresses a specific need (departments, search, details, random, highlights, comparisons), and the count is within the ideal range of 3-15.

Completeness4/5

The tool set covers the main museum browsing workflows: get departments, search by various criteria, get details, highlights, random, and comparison. Missing features might include artwork filtering by medium or sorting, but the current set supports core discovery and exploration without critical gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues