Skip to main content
Glama

smithsonian-mcp-server

by io.github.cyanheads

Get Smithsonian Object

smithsonian_get_object
Read-onlyIdempotent

Fetch a normalized catalog metadata projection for a Smithsonian object by its record_id (from smithsonian_search_objects results). Returns the exposed catalog fields — title, dates, description, makers, materials, dimensions, places, cultures, topics, exhibitions, credit line, identifiers, rights, and a media summary. The media summary is a count; full image URLs come from smithsonian_get_media.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesObject record_id from smithsonian_search_objects results (e.g. "nasm_A19670093000").

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
datesNoAll date fields in the catalog record.
errorNoPresent when the call failed. Absent on success.
placeNoGeographic place associations.
titleNoObject title.
is_cc0NoTrue when the object metadata is CC0 (open access). The Smithsonian Open Access corpus is CC0 throughout, so this flag rarely varies — read media_summary.has_cc0_images to predict whether smithsonian_get_media returns images.
makersNoAll named parties associated with this object.
topicsNoSubject and topic terms.
cultureNoCulture associations.
materialsNoPhysical material descriptions.
record_idNoUnique object identifier.
unit_codeNoMuseum unit code.
dimensionsNoDimension and measurement strings.
credit_lineNoAttribution or credit string.
descriptionNoBest available prose description (Summary, Physical Description, or Brief Description notes).
exhibitionsNoExhibition history.
identifiersNoAll accession and catalog identifiers.
museum_nameNoFull museum name. A few rarely-indexed archive sub-unit codes have no mapped name and fall back to the raw unit code.
record_linkNoCanonical Smithsonian Institution URL for this object.
media_summaryNoMedia availability summary. Call smithsonian_get_media for full image URLs.
object_rightsNoRights statement from the catalog.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds value by specifying the return is a 'normalized catalog metadata projection' with a list of exposed fields and that the media summary is a count, which is beyond what annotations convey. No contradictions with 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?

The description is two sentences with zero fluff. The core purpose is front-loaded, and the note about media summary and smithsonian_get_media is logically placed. Every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool is a simple read-only fetch with a single parameter and has an output schema (not explicitly provided but declared), the description covers the essential context. It lists the returned fields and clarifies the media summary behavior. Minor gaps like error handling or authentication requirements are not critical for a read-only idempotent tool with strong annotations.

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

Parameters3/5

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

Schema description coverage is 100% — the id parameter is described with an example (e.g., 'nasm_A19670093000'). The description reuses 'record_id' from search results, which matches the schema. It doesn't add more detail than the schema already provides, so baseline 3 is appropriate.

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 the tool fetches a normalized catalog metadata projection for a Smithsonian object by record_id, with specific resource and verb. It distinguishes from siblings by noting the media summary is a count and full image URLs come from smithsonian_get_media, so an agent can tell it apart from smithsonian_get_media.

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 explicitly ties this tool to smithsonian_search_objects results, indicating when to use it (after searching). It also mentions that full image URLs come from smithsonian_get_media, implicitly routing away from that sibling. While it doesn't explicitly state when-not to use other tools, the context is clear enough.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All smithsonian-mcp-server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.6/5.0
Disambiguation5/5

Each tool has a clearly distinct role: browsing an exact category, searching free-text, retrieving object metadata, fetching media, listing vocabulary, and finding related objects. Overlaps like browse_category vs search_objects are well-explained with explicit guidance on when to use each, eliminating ambiguity.

Naming Consistency5/5

All tools follow the same pattern: 'smithsonian_' prefix with lowercase snake_case verb_noun names (e.g., browse_category, get_media, list_terms). The naming is perfectly uniform and intuitive.

Tool Count5/5

Six tools cover the full spectrum of Smithsonian discovery and retrieval without bloat. Each tool addresses a distinct need, and the count is well-scoped for a read-only museum API.

Completeness5/5

The surface covers search, exact-category browsing, term vocabulary enumeration, object metadata retrieval, media access, and related-object discovery. There are no obvious dead ends—record IDs flow from search to other tools, and gaps like non-CC0 media are explicitly handled.

Resources