Skip to main content
Glama

One component, whole

research_component
Read-onlyIdempotent

The component a hit points at (uuid or event id): every event with its summary and structured fields, the evidence behind the quality tier, links to the Library of Congress page PDFs and to snewpapers.com (1 token). include_text=true adds the full text: 3 tokens, charged once per component - be selective, never page through full texts. component_id is a uuid or {uuid}_evt_N; the response echoes the requested event index so a client can highlight it. Caution components return only a description and links while guarded=true; for research the better experience is guarded=false - ask the researcher once, at the start of the session, then pass it on every call. If your own content rules cannot handle such historical text, do not fetch unguarded - give the researcher the site link. include_boxes=true (free) adds the component's rectangles per page as fractions of the page image, for drawing it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "component_id": "<component_id>"
    },
    "name": "research_component"
  }
}

Input Schema

NameRequiredDescriptionDefault
guardedNo
component_idYes
include_textNo
include_boxesNo

Output Schema

NameRequiredDescriptionDefault
cityNo
lccnYes
uuidYes
yearYes
boxesNoOnly with include_boxes=true: rectangles per page as fractions of the page image (a cross-page story has an entry per page; a story in two columns has two rectangles on that page); null otherwise
labelYes
linksYes
pagesNo
stateNo
countyNoA title can span several (LoC data)
eventsYes
thumbsNonull until the thumbnail stage is re-wired for the new pipeline
cautionNo
contentNoFull text (tables spliced in), only with include_text=true; withheld for caution components under guarded=true
citationYesCite from this; the same with or without text
evidenceYes
resolvedNofalse: the extractor judged it incomplete — a lost opening, or continued in a later issue
newspaperYes
char_countNo
issue_dateYes
issue_uuidYes
event_countYes
issue_pagesNoPage count of the whole issue (this component's own pages are `pages`); null when the issue has no page images recorded
embed_worthyNo
quality_tierYes
chain_membersNo>= 2: merged across pages; the evidence below is the WORST case over the fragments
tokens_chargedYesWhat this call cost (full text: 3 once per component, then 0)
quality_tier_whyNoThe first condition that decided a non-green tier (e.g. fuzz_lt_92, lt80_gt_0.05); "green" for green
tokens_remainingYesYour balance after it
caution_descriptionNo
requested_event_idxNoEcho of the event in the id you asked with

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, and closed-world behavior, but the description adds substantial operational context beyond them. It discloses token costs for the base response and include_text, the one-time charge per component, the free include_boxes behavior, guarded-mode limitations, the response echoing the requested event index, and a caution about content rules and unguarded historical text.

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 front-loaded with the core purpose and output scope, and most sentences carry useful behavioral or cost information. It is somewhat dense and repeats the component_id format after already mentioning uuid/event id, but the length is justified by the four parameters and the guarded/text/box options.

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 an output schema, annotations covering safety, and four parameters with no schema descriptions, the description is complete enough for correct invocation. It covers purpose, parameter semantics, token costs, guarded-mode implications, content-rule cautions, and output-related behavior such as the echoed event index.

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

Parameters5/5

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

Schema description coverage is 0%, so the description carries the full burden, and it explains all four parameters meaningfully. It defines component_id as a uuid or {uuid}_evt_N, explains include_text’s full-text cost and one-time charge, explains include_boxes as free page-relative rectangles, and clarifies guarded-mode behavior and the recommended guarded=false setting for research.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as the component a search hit points at and enumerates what is included: events, summaries, structured fields, quality-tier evidence, and PDF/snewspaper links. It does not explicitly name sibling alternatives, so it falls short of the top score for sibling differentiation, but the singular component scope is still specific.

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 gives useful usage guidance for parameters: include_text should be used selectively and never to page through full texts, guarded=false is better for research, and unguarded fetching should be avoided when content rules cannot handle historical text. However, it does not explicitly say when to choose this tool over alternatives such as research_components or research_search, leaving tool-selection guidance implied rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources