Skip to main content
Glama
smeet666

mcp-libraryofcongress

Read a record

get_item
Read-onlyIdempotent

Fetch a Library of Congress record by its identifier, with options for citations, resources, or full metadata. Use pagination for long descriptions.

Instructions

Read one Library of Congress record by its identifier, as returned by search_items or search_newspapers. An identifier can carry slashes: a single newspaper issue is named by its paper, its date and its edition together. Sections are opt-in: 'basic' is the default and covers what a description needs. 'date' carries only the precision the record's own words support, and 'date_stated' repeats those words, which can be a span of years the record was filed at the opening of. Where the Library has established no date it files the record under a cataloguing code, which 'date_code' carries while 'date' and 'year' stay null. 'citations' returns the ready-made citations the Library publishes for the record. 'resources' lists the served copies, such as page images and downloadable files. 'full_metadata' returns every field the Library publishes for the record, which is large and rarely needed. A long description paginates: when 'next_offset' is not null, call again with 'offset' set to it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
offsetNoWhere to resume the description.
sectionsNoWhich parts to return. Each one beyond 'basic' adds to the size of the answer.
identifierYesRecord identifier, such as '2017645459' or 'sn83045462/1929-02-03/ed-1'.
max_description_charsNoCharacters of the description to return in one call.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
itemYes
notesYes
offsetYes
rightsYesWhat the Library says about reuse. Null when it says nothing, which is not permission.
part_ofYesCollections and divisions the record sits in.
languageYes
locationYes
subjectsYes
citationsNo
resourcesNo
repositoryYesWhere the original is held.
call_numberYes
descriptionYes
next_offsetYesPass as 'offset' to read the rest of the description. Null when it ends here.
full_metadataNo
notes_on_recordYesNotes the Library published about the record itself, less any whose words the description already carries. The Library assembles the description of some records out of these notes, and those records would otherwise return one text under two names.
Behavior2/5

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

The description includes extensive behavioral details, but several of them are false: it mentions 'date', 'date_stated', 'date_code', and 'year' as section options, yet the schema's enum only allows 'basic', 'citations', 'resources', and 'full_metadata'. This actively misleads an agent about the tool's behavior, which is worse than omitting details. The readOnlyHint and idempotentHint annotations are accurate, but the description's incorrect claims undermine transparency.

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

Conciseness3/5

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

The description is organized with the purpose first, then identifier details, section explanations, and pagination. However, a significant portion is devoted to explaining 'date', 'date_stated', 'date_code', and 'year'—all of which are not valid section values. This makes the description unnecessarily long and misleading, though the structure itself is logical.

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

Completeness3/5

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

The description covers many important aspects: identifier format, pagination, and the purpose of each valid section. With an output schema present, it need not describe return values. However, it omits any mention of the actual allowed section enum and instead lists invalid options, leaving an agent with inaccurate information about how to use the tool. This is a significant completeness gap.

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

Parameters2/5

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

The input schema already describes all four parameters with 100% coverage, giving a baseline of 3. The description does add useful semantics for 'identifier' (slash format) and 'offset' (pagination), but it incorrectly lists non-existent section values, which would cause an agent to pass invalid inputs. This misinformation cancels out the added value and makes the description a net negative for parameter understanding.

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 begins with 'Read one Library of Congress record by its identifier', clearly stating the verb, resource, and scope. It also distinguishes itself from sibling tools by noting that the identifier is 'as returned by search_items or search_newspapers', making the tool's purpose unmistakable.

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 provides clear context on when to use the tool: after obtaining an identifier from search tools. It also explains pagination ('call again with offset set to it') and section options. However, it does not explicitly state when not to use this tool or compare it against alternatives like list_collections, so it falls short of a 5.

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/smeet666/mcp-libraryofcongress'

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