Skip to main content
Glama
easyscholar-mcp

easyscholar-mcp

by tanskeran

journal_ranks

Look up impact factors, JCR quartiles, and CAS zones for multiple journals in one request (up to 50), returning consistent results per journal.

Instructions

Look up several journals at once (max 50; ~0.6 s between requests). Same output per journal as journal_rank.

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": {
      "publication_names": "<publication_names>"
    },
    "name": "journal_ranks"
  }
}

Input Schema

NameRequiredDescriptionDefault
publication_namesYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two real behavioral traits: a hard cap of 50 journals and roughly 0.6 s of latency between requests, which signals rate limiting. It is silent on what happens for unrecognized publication names, whether results are ordered like the input, and authentication needs.

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 short clauses, zero filler, with the batching purpose and the cap front-loaded before the reference to the sibling. Every element carries usable information.

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?

An output schema exists and the description correctly defers return-value detail to journal_rank, so the omission is appropriate rather than a gap. The only missing piece an agent would want is failure behavior for names that cannot be resolved.

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 coverage is 0% and the single parameter is a bare string array, so the description must compensate; it does so by identifying the entries as journal identifiers and constraining the array to a maximum of 50. It does not say whether entries are names, ISSNs, or abbreviations, which leaves some ambiguity.

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 a specific verb and resource ('Look up several journals at once') and frames the batch nature against the sibling journal_rank, so an agent can tell it apart from the single-journal tool. It is clear but does not name journal_rank as the explicit single-item alternative.

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 max-50 cap and '~0.6 s between requests' note give practical guidance on when this bulk call is appropriate, and 'Same output per journal as journal_rank' implies parity with the single lookup. However, it never explicitly says to use journal_rank for a single lookup or what to do when more than 50 names are needed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools