Skip to main content
Glama

Newspaper titles with coverage

research_titles
Read-onlyIdempotent

Which papers exist, which are processed, and how much: filter by state (full name, e.g. "virginia"), city, county, ethnicity (the values the ethnicity facet returns, e.g. "African American", "German") or a name (q, contains, case-insensitive); returns total, refreshed_at and the page of titles (limit/offset); county, ethnicity, or a name (q; a masthead can span several lccns, each row carries its own). Untouched titles are listed with processed_issues=0. The lccn is the key used everywhere else. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "research_titles"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
cityNo
limitNo
stateNo
countyNo
offsetNo
ethnicityNo
english_onlyNo
processed_onlyNo

Output Schema

NameRequiredDescriptionDefault
totalYesTitles matching the filters
titlesYes
refreshed_atNoWhen the coverage table was last rebuilt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. Beyond that the description adds genuine context: the response shape (total, refreshed_at, page of titles), the fact that untouched titles appear with processed_issues=0, that lccn is the join key used elsewhere, and that queries are free. Only the english_only default-on filter behavior is left undisclosed.

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

Conciseness2/5

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

The front-loaded purpose is good, but the body is a single semicolon-chained run-on containing a garbled, redundant fragment ('; county, ethnicity, or a name (q; a masthead can span several lccns, each row carries its own)') that restates the already-listed filters instead of adding information. Parsing cost is high for the payload delivered.

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?

An output schema exists, so return values need not be spelled out (the description covers them anyway). For a 9-parameter, 0%-schema-coverage tool, however, omitting both boolean filters — especially english_only defaulting to true — leaves an agent able to silently mis-scope its query.

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

Parameters3/5

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

Schema description coverage is 0% across 9 parameters, so the description must carry the load: it explains state (full name, e.g. 'virginia'), city, county, ethnicity, q (substring, case-insensitive), and limit/offset. It does not mention processed_only or english_only, and english_only silently defaults to true, which is a non-obvious result-shaping behavior the agent cannot learn from the bare schema.

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?

Opens with a concrete statement of the resource and what it conveys ('Which papers exist, which are processed, and how much'), then enumerates the filter dimensions. It is clearly a filtered list of newspaper titles with issue counts, distinguishable from research_title (singular detail lookup) by the enumerable filter set, though it never names a sibling explicitly.

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?

Usage is implied through the filter list and one useful cross-reference ('the values the ethnicity facet returns'), which tells the agent to call research_facets first for valid ethnicity values. 'Free' hints at a cost-based preference over paid search endpoints. However, there is no explicit when-to-use/when-not statement and no routing to research_search or research_title for different needs.

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