Skip to main content
Glama

apibase

by io.github.whiteknightonhorse
OverviewDiscussionsAdmin

Search Smithsonian Collections

smithsonian.collection.search
Read-onlyIdempotent

Full-text search across 11M+ records from 19 Smithsonian museums — art, artifacts, scientific specimens, archives. Filter by type (objects/species/archives/books/online_media/events/places), sort by relevancy/newest/updated/random, and CC0-only by default. Covers National Museum of Natural History, Air and Space, American Art, Portrait Gallery, Freer|Sackler, and more (Smithsonian Open Access, CC0 subset)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesFull-text search query. Example: "dinosaur", "picasso", "apollo 11". Supports EDAN query syntax (field:value, AND/OR).
rowsNoNumber of results to return (1-100, default 10).
sortNoSort order for results. Default: relevancy.
typeNoFilter by record type. E.g. "objects" for 3D objects, "species" for scientific specimens.
startNoOffset for pagination (default 0). Useful with rowCount from previous call.
cc0_onlyNoFilter results to CC0-licensed records only (default true). Set false to include all records with their license field.
online_media_typeNoFilter to items that have media of a specific type.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
errorNoPresent only when the call failed. Includes error code, message, request_id, and any provider-specific extras.
resultNoTool response payload. Shape varies per tool — consult the tool description and inputSchema. May be an object, array, string, or number depending on the upstream provider response.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added
  6. Removed
  7. Added
  8. Removed
  9. Added
  10. Removed
  11. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds behavioral context like 'CC0-only by default' and the scope of institutions covered, which goes beyond the annotations. 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 well-structured sentences, front-loading the core purpose and then providing details on filters and scope. Every sentence adds value without redundancy.

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 the tool's 7 parameters with 100% schema coverage and an output schema, the description fully covers the main use case, filter options, and default behavior. It is complete for an agent to understand and invoke the tool correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaningful context by explaining the types of records (e.g., 'objects' as 3D objects, 'species' as scientific specimens) and the default CC0 filter, enhancing understanding beyond the 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 'Full-text search across 11M+ records from 19 Smithsonian museums' and lists specific filterable types (art, artifacts, specimens, etc.). It distinguishes itself from the sibling tool 'smithsonian.collection.record' by focusing on search across the entire collection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for broad search but does not explicitly mention when to use this tool versus 'smithsonian.collection.record' or other alternatives. It provides clear context on filters but no guidance on exclusions.

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

All apibase toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources