libofcongress-mcp-server

Get LOC Item

libofcongress_get_item

Read-only

Retrieve the full metadata record for a specific LOC digital item. Returns contributors, subjects, summary, languages, locations, rights information, physical description, call number, original and online formats, access restrictions, former catalog IDs, notes, related items, and links to digital resources (TIFF, JPEG, PDF) for items with digital surrogates. Use after libofcongress_search on a result whose is_item is true. Pass the result id verbatim — it may be a simple ID or a slash-separated newspaper path; do not prepend the loc.gov URL. Non-item results (is_item: false) — collections, exhibits, guides, newspaper pages — have no item record and cannot be retrieved here.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`item_id`	Yes	LOC item id from a libofcongress_search result's "id" field (where is_item is true). A simple ID ("2009632251", "2005691065") or a slash-separated path for newspaper pages ("sn95047246/1935-09-05/ed-1"). Pass the id verbatim; do not prepend the loc.gov URL or an "item/" prefix.

Output Schema

TableJSON Schema

Name	Required	Description
`url`	No	Canonical LOC item URL.
`date`	No	Publication or creation date.
`error`	No	Present when the call failed. Absent on success.
`notes`	No	Descriptive notes and annotations from catalogers.
`title`	No	Item title.
`item_id`	No	LOC item ID as resolved by the service (matches the input item_id).
`summary`	No	Cataloger's abstract of the item's subject and historical context.
`languages`	No	Languages of the item (e.g., "english").
`locations`	No	Places the item depicts or originates from (e.g., "united states").
`former_ids`	No	Superseded catalog identifiers or URLs this item was previously known by.
`call_number`	No	LOC call number — the shelf location for requesting the physical original.
`contributors`	No	Contributors, creators, or photographers as LOC catalogs them, role included (e.g., "Washington, George, 1732-1799 (Author)"). One person can appear once per role. Empty when LOC lists none.
`related_items`	No	IDs or URLs of related LOC records for follow-up retrieval; a title stands in for a related record LOC gives neither for.
`online_formats`	No	Formats the digitized surrogate is available in (e.g., "image").
`resource_links`	No	URLs to downloadable digital files (TIFF, JPEG, PDF). Empty when no digital surrogate exists.
`original_formats`	No	Material types of the original (e.g., "photo, print, drawing").
`subject_headings`	No	LCSH subject headings assigned to this item.
`access_restricted`	No	True when LOC restricts access to the original. Absent when upstream omits it.
`rights_information`	No	Rights and reproduction statement for this item.
`physical_description`	No	Physical or technical description of the original item.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedSep 22, 2026

changedInput schema / properties / item_id / description

Previous value: -"LOC item id from a libofcongress_search result's \"id\" field (where is_item is true). A simple ID (\"2009632251\", \"loc.pnp.ppmsc.02404\") or a slash-separated path for newspaper pages (\"sn95047246/1935-09-05/ed-1\"). Pass the id verbatim; do not prepend the loc.gov URL or an \"item/\" prefix."New value: +"LOC item id from a libofcongress_search result's \"id\" field (where is_item is true). A simple ID (\"2009632251\", \"2005691065\") or a slash-separated path for newspaper pages (\"sn95047246/1935-09-05/ed-1\"). Pass the id verbatim; do not prepend the loc.gov URL or an \"item/\" prefix."

changedOutput schema / properties / contributors / description

Previous value: -"Names of contributors, creators, or photographers."New value: +"Contributors, creators, or photographers as LOC catalogs them, role included (e.g., \"Washington, George, 1732-1799 (Author)\"). One person can appear once per role. Empty when LOC lists none."

changedOutput schema / properties / related_items / description

Previous value: -"IDs or URLs of related LOC items for follow-up retrieval."New value: +"IDs or URLs of related LOC records for follow-up retrieval; a title stands in for a related record LOC gives neither for."

First observedSep 19, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavioral detail about what the response includes — contributors, subjects, rights, formats, access restrictions, and digital resource links — plus the caveat about items without digital surrogates.

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

Conciseness4/5

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

The description is longer than average, but every section earns its place: purpose first, then return contents, then usage rules and exclusions. The structure is dense but scannable, with clear guidance embedded naturally.

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 a single required parameter, a fully documented schema, an output schema present, and annotations covering read-only behavior, the description adds the remaining operational context: when to call it, what ids are valid, and what cannot be fetched. An agent has everything needed to select 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% and the schema itself is rich, giving a baseline of 3. The description reinforces key invocation semantics beyond the schema: pass the result id verbatim, the id may be a simple ID or a slash-separated newspaper path, and must come from an is_item:true search result.

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 retrieves the full metadata record for a specific LOC digital item and enumerates the returned data categories. It also distinguishes itself from related tools by explicitly saying non-item results like collections, exhibits, guides, and newspaper pages cannot be retrieved here.

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

Usage Guidelines5/5

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

The description gives explicit usage context: use this tool after libofcongress_search on a result whose is_item is true. It also states what not to do, including passing non-item results and not prepending the loc.gov URL or an 'item/' prefix.

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

All libofcongress-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.