Skip to main content
Glama

One title in depth

research_title
Read-onlyIdempotent

One paper (by lccn): processed issues per year against the Library of Congress span, so a missing year inside the span means "exists, not processed"; label and tier mix. With year, the processed issue dates in that year. Free.

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": {
      "lccn": "<lccn>"
    },
    "name": "research_title"
  }
}

Input Schema

NameRequiredDescriptionDefault
lccnYes
yearNo

Output Schema

NameRequiredDescriptionDefault
yearNoEcho of the ?year= drill-down, when asked
titleYes
labelsYesdocs per label for this title
quality_tiersYesdocs per tier for this title; red is reported here and never served
issues_by_yearYesProcessed issues per year. A year inside the LoC span with no entry is "exists, not processed".
issue_dates_in_yearNoProcessed issue dates in that year (the finest coverage answer; one title at a time)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower and the description still adds real semantic context: a missing year inside the LoC span means 'exists, not processed' rather than nonexistent, which is a crucial interpretation rule an agent would otherwise get wrong. 'Free' also signals there is no cost/rate-limit concern. It does not cover behavior for an invalid or unknown lccn.

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?

Very compact and front-loaded: the subject ('One paper (by lccn)') comes first, followed by the default behavior and then the year-modifier, with no filler sentences. Density comes at a cost — 'label and tier mix' and the dangling 'Free.' are telegraphic and rely on the reader already knowing the domain jargon.

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?

For a two-parameter, single-required-argument lookup with an output schema (so return shape need not be described), the description covers the key semantics: what identifies the title, what the default response means, and how year changes it. The remaining gaps — lccn format and unknown-lccn handling — are modest given the tool's simplicity and the annotations covering safety.

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 description coverage is 0%, so the description must carry the parameter meaning, and it largely does: 'by lccn' identifies the single paper, and 'With year, the processed issue dates in that year' explains exactly what the optional year parameter switches on versus the default per-year breakdown. What is missing is lccn format/validation and behavior when year falls outside the span.

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 states the resource precisely: 'One paper (by lccn)' with per-year processed issues against the LoC span, plus label and tier mix, and issue dates when a year is supplied. The retrieval verb is left implicit (the tool never says 'get'/'fetch'), but the singular scope and the enumerated payload make the purpose unmistakable. Sibling differentiation is only implied by the singular vs. plural (research_titles) rather than stated.

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 year clause effectively encodes usage: omit year for the aggregated per-year view, supply year to drill into processed issue dates for that year. However, there is no explicit guidance on when to pick this over research_titles or research_search, and no statement of preconditions (e.g., needing a valid LCCN obtained elsewhere).

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