easyscholar-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EASYSCHOLAR_SECRET_KEY | Yes | Your easyScholar secret key, obtained from your easyScholar account (Personal Center → Open API). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| journal_rankA | 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. |
| journal_ranksA | Look up several journals at once (max 50; ~0.6 s between requests). Same output per journal as journal_rank. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools are clearly separated by cardinality: journal_rank handles one title, journal_ranks handles up to 50, and both descriptions state this explicitly. The singular/plural distinction is the only potential confusion point, but the descriptions make selection straightforward.
Both names follow the same noun-based pattern with a singular/plural pair (journal_rank / journal_ranks), which is predictable and readable. The only minor deviation is that neither uses a verb prefix like get_ or lookup_, so the action must be inferred from the noun.
The domain is deliberately narrow (journal metric lookup), so two tools are defensible, but it sits at the thin end where a single tool with a list parameter could have covered both cases. The batch tool does earn its place given the ~0.6s per-request throttle.
Core metric retrieval is well covered, including caching, spelling fallbacks, and rich metric keys. However, there is no way to search or discover journals by keyword, ISSN, or category, so an agent that doesn't already know the exact title has a dead end beyond the automatic respelling attempts.