Skip to main content
Glama
easyscholar-mcp

easyscholar-mcp

by tanskeran

journal_rank

Look up a journal's impact factor, JCR quartile, and CAS (中科院) zone via easyScholar to evaluate publication venues and verify indexing status.

Instructions

Look up one journal's impact factor and quartiles/zones via easyScholar (查期刊影响因子和分区).

publication_name: journal title, e.g. "NeuroImage: Clinical", "Annals of Neurology".

If the name is not found as given, a few respellings are tried automatically (drop leading "The", '&' <-> 'and', drop punctuation, ':' -> '-'); "matched_name" then shows the spelling that matched. Found results are cached locally for 30 days.

Returns {"query", "found", "metrics", "custom_ranks"?, "matched_name"?} or {"found": false, "tried", "hint"} / {"found": false, "error"}. metrics keys: impact_factor (JCR IF), impact_factor_5y, jcr_quartile (Q1-Q4), jci, esi_field, cas_zone (中科院分区升级版), cas_subcategory_zone, cas_top, cas_zone_basic (中科院基础版), cas_warning (中科院预警), xinrui_zone (新锐分区), ssci_quartile, esci_quartile, ei, pku_core, cssci, cscd, ccf. Only keys easyScholar has data for are present; values are strings. If found is false, do not retry the spellings in "tried"; try the abbreviation or full title.

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_name": "<publication_name>"
    },
    "name": "journal_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
publication_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the whole burden and does so: it discloses normalization fallbacks ('&' <-> 'and', ':' -> '-'), that results are cached locally for 30 days, the exact success/failure payload shapes, and that metric values are strings with only available keys present. This goes well beyond a bare purpose statement.

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?

Front-loaded with the purpose, then param, then matching rules, then return shape and failure handling – a logical order. The long metrics-key enumeration is verbose in prose form, but it substitutes for a missing output schema, so most of it earns its place.

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

Completeness5/5

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

For a one-parameter lookup with no output schema and no annotations, everything an agent needs is present: return keys, failure variants, matching behavior, and caching. No output schema exists, so explaining return values here is appropriate rather than redundant.

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% for the single parameter, so the description must compensate; it defines publication_name as a journal title with concrete examples ("NeuroImage: Clinical", "Annals of Neurology") and the accepted variants. It stops short of stating format constraints (length, whether ISSN is accepted).

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

Purpose5/5

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

Names a specific verb and resource ("Look up one journal's impact factor and quartiles/zones") and pins the source (easyScholar), with the singular "one journal" implicitly contrasting with the plural sibling journal_ranks. An agent knows immediately what it returns.

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?

Gives clear operating context: use for a single journal title, plus recovery guidance (automatic respellings, and on found=false "do not retry the spellings in 'tried'; try the abbreviation or full title"). No explicit statement of when to prefer journal_ranks for batch lookups, so not a 5.

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