Skip to main content
Glama
malkreide

swiss-cultural-heritage-mcp

by malkreide

heritage_get_artist

Read-onlyIdempotent

Fetch full SIKART artist records with biography, life dates, locations, and related links for Swiss cultural heritage research.

Instructions

Ruft den vollständigen SIKART-Datensatz zu einer Künstler·in ab.

Args: params (ArtistDetailInput): - artist_id (str): SIKART-ID (HAUPTNR aus heritage_search_artists) - response_format: 'markdown' oder 'json'

Returns: str: Vollständiges Profil mit Lebensdaten, Orten, Kurzbiografie und Links.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paramsYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds return content details (life data, locations, biography, links) beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sections: first line states purpose, then args and returns. No wasted words, front-loaded.

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?

With annotations, input schema, and output schema (present), the description covers purpose, parameters, and return value sufficiently for a simple detail retrieval tool.

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

Parameters4/5

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

Despite schema description coverage being 0%, the description explains the two parameters: artist_id (source from heritage_search_artists) and response_format (options markdown/json). Adds value over bare 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?

Description clearly states the action ('abrufen') and resource ('vollständigen SIKART-Datensatz zu einer Künstler·in'). Differentiates from sibling tools like heritage_search_artists (search vs detail retrieval).

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?

Mentions that artist_id comes from heritage_search_artists and response_format options. Provides usage context but does not explicitly state when not to use or list alternative tools.

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/malkreide/swiss-cultural-heritage-mcp'

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