Skip to main content
Glama

List journals

list_journals
Read-onlyIdempotent

Publication venues ranked by linked bibliography records, with ISSN and catalogue links.

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_journals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoDefault 50, max 200
offsetNo
keywordNoFilter on the journal title; every word must match, quote a phrase

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / keyword / description
      Previous value: -"Substring filter on the journal title"New value: +"Filter on the journal title; every word must match, quote a phrase"
  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. Changed1 schema field changed
    • addedInput schema / properties / keyword / maxLength
      Added value: +1000
  5. First observed

TDQS

C2.8/5.0
Behavior3/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. The description adds that results are ranked by linked bibliography records and include ISSN and catalogue links, which is useful return-content context, but it does not discuss pagination or ordering details beyond the ranking phrase.

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?

It is a single compact sentence with no filler. However, the sentence is not front-loaded with the action and is somewhat dense and ambiguous.

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?

For a simple list tool with annotations covering safety and a schema covering most parameters, the description gives the ranking and included fields. It still lacks usage guidance and any parameter or pagination context, so it is adequate but incomplete.

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 coverage is 67%: limit and keyword are documented in the schema, while offset has only bounds and no description. The description mentions no parameters and does not compensate for the undocumented offset or clarify keyword matching beyond the schema.

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 identifies the resource as publication venues/journals and says they are ranked by linked bibliography records, but it never states the action "list" or scope, and it does not distinguish this from sibling list_* tools. The name and title carry the verb, so the description itself is only partially clear.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance, exclusions, or alternatives are named. An agent must infer that this is for browsing journals rather than searching or fetching a specific journal.

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.