Skip to main content
Glama

What you can filter on

research_vocabulary
Read-onlyIdempotent

Types and themes (whole) and the top keywords for a label, optionally narrowed by lccn, state and years. Call before filtering on a term you have not seen. 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_vocabulary"
  }
}

Input Schema

NameRequiredDescriptionDefault
lccnNo
sizeNo
labelNo
stateNo
year_toNo
year_fromNo

Output Schema

NameRequiredDescriptionDefault
labelYes
typesYesThe extractor's per-label type vocabulary, complete: term → doc count
themesYesOnly the literary genres carry themes (letter_to_editor, story, poem, literary); empty otherwise
keywordsYesFree-text keywords, long-tailed: the top `size` (default 50)
total_docsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/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 the safety profile is covered. The description adds one genuinely useful item annotations do not cover — 'Free', signaling no billing concern — plus the framing as a pre-filter discovery step. It does not describe result size, limits, or how the narrowing filters interact, and return shape is left to the output schema.

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?

Two compact sentences with no filler; the scope statement comes first and the usage trigger second. The terse '(whole)' parenthetical is the only fragment that costs comprehension rather than saving words.

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

Completeness2/5

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

With six undocumented parameters and an output schema handling returns, the description should explain at least the filter dimensions and the result-size control, but 'size' and the meaning of narrowing by lccn/state/years go unaddressed. An agent can fire the call, but cannot reason about what each argument does or how the result set is bounded.

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?

Schema description coverage is 0%, so the description must carry parameter meaning, and it only names lccn, state, and years without explaining formats, accepted values, or inclusive/exclusive year bounds. It omits the 'size' parameter entirely and never clarifies that 'label' determines which keywords are returned, leaving the majority of the six parameters semantically undefined.

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

Purpose3/5

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

The description conveys the resource indirectly ('Types and themes... top keywords for a label') but never uses a clear verb like 'list' or 'return', and the parenthetical '(whole)' is cryptic. An agent can guess this is a vocabulary/facet lookup, but the phrasing is oblique rather than a specific verb+resource statement, and no sibling (research_facets, research_labels) is named for differentiation.

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?

'Call before filtering on a term you have not seen' gives a concrete, actionable trigger for when to use the tool. There is no explicit when-not guidance and no named alternative among the sibling research_* tools, which keeps it 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources