Skip to main content
Glama

List subjects

list_subjects
Read-onlyIdempotent

Subject headings (LCSH or free tags) ranked by distinct research-item count. Feed a heading into search_research_items.subject.

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": "list_subjects"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50, max 300
offsetNo
keywordNoFilter on the heading; every word must match, quote a phrase
vocabularyNolcsh, tag, or unspecified: every other heading (mostly places with no vocabulary)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Substring filter on the subject heading"New value: +"Filter on the heading; every word must match, quote a phrase"
    • changedInput schema / properties / vocabulary / description
      Previous value: -"Only Library of Congress headings or only free tags"New value: +"lcsh, tag, or unspecified: every other heading (mostly places with no vocabulary)"
    • changedInput schema / properties / vocabulary / enum
      Previous value: -[
      -  "lcsh",
      -  "tag"
      -]New value: +[
      +  "lcsh",
      +  "tag",
      +  "unspecified"
      +]
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
  3. Changed1 schema field changed
    • removedInput schema / properties / limit / maximum
      Removed value: -9007199254740991
  4. Changed2 schema fields changed
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
    • addedInput schema / properties / vocabulary
      Added value: +{
      +  "description": "Only Library of Congress headings or only free tags",
      +  "enum": [
      +    "lcsh",
      +    "tag"
      +  ],
      +  "type": "string"
      +}
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description still adds genuinely useful behavior beyond them: results are ranked by distinct research-item count, which tells the agent the first page is the most-used headings. Pagination/limit behavior (max 300) is left entirely to the schema.

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

Conciseness5/5

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

Two sentences, zero filler. The resource and ranking rule come first, and the actionable next step follows, so the agent gets the essentials immediately.

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 four-parameter, no-required-argument list tool with annotations and no output schema, this covers what the tool returns, how it is ordered, and what to do with the result. Only pagination semantics and the exact response shape are unaddressed, which is minor here.

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 coverage is 75%, so the baseline is 3. The description clarifies the domain of the vocabulary parameter (LCSH vs free tags) and that keyword filtering applies to the heading itself, but limit and offset are documented only in the schema and the description adds no format hints.

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 names the resource precisely — subject headings, either LCSH or free tags — and states the ordering rule (ranked by distinct research-item count). An agent can tell this apart from list_categories or list_journals without opening the schema, though it never explicitly contrasts itself with those siblings.

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?

It gives a concrete downstream workflow: feed a returned heading into search_research_items.subject. That is real usage context rather than implied usage. It stops short of exclusions or saying when a different list_* tool is the better choice.

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.