Skip to main content
Glama

Find journals for a manuscript

find_journals
Read-onlyIdempotent

Find journals to submit a manuscript to: paste the abstract (or title and abstract) and get the journals that published the most similar papers in recent years, from OpenAlex. Each journal comes with its publisher, ISSN, how many similar papers it published (with examples), whether it is fully open access, whether it is in DOAJ and MEDLINE, the APC OpenAlex lists, two-year mean citedness, h-index, yearly output, and flags worth checking (no ISSN, stopped publishing, output that tripled in a year, open access but not in DOAJ). Quartiles (Q1–Q4) are NOT included and must not be stated from memory: each result has an sjr link (Scopus quartile) and an mjl link (Web of Science) where the user reads them. Flags are reasons to check, never a verdict that a journal is predatory. A website listed here is not verified: hijacked journals copy real ones, so the journal is best reached from its publisher, DOAJ or SJR page. Pass keywords with English words when the abstract is not in English.

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": {
      "abstract": "<abstract>"
    },
    "name": "find_journals"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearsNoSearch papers from this many past years up to now.
abstractYesThe abstract, or the title on the first line followed by the abstract.
keywordsNoEnglish search keywords. Recommended when the abstract is not in English.
max_apc_usdNoLeave out journals whose listed APC is above this.
max_resultsNoNumber of journals, 1–15.
open_access_onlyNoOnly fully open-access journals.

Output Schema

NameRequiredDescriptionDefault
csvYes
quotaYes
statsYes
windowYes
resultsYes
warningsYes
data_noteYes
safety_noteYes
search_termsYes
flag_meaningsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare read-only, idempotent, open-world; the description adds substantial interpretation guidance beyond them: flags are 'reasons to check, never a verdict that a journal is predatory', a website may be hijacked and the journal should be reached via publisher/DOAJ/SJR, and quartiles must come from the `sjr`/`mjl` links rather than memory. This is exactly the kind of safety and result-interpretation context annotations cannot carry.

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?

Purpose and the critical caveats are front-loaded and every warning sentence earns its place. However the long mid-sentence enumeration of return fields (publisher, ISSN, APC, h-index, yearly output, etc.) overlaps heavily with the existing output schema and could be tightened.

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?

Given six parameters, an output schema, and rich annotations, the definition covers what matters: input format, the English-keyword escape hatch, the quartile prohibition, and the predatory/hijacked-journal caveats. The return-value enumeration is redundant with the output schema, but nothing an agent needs in order to call it correctly is missing.

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 description coverage is 100%, so all six parameters are already documented in the schema, including the `keywords` fallback for non-English abstracts. The description restates the abstract/keywords handling but adds no syntax, format, or trade-off detail beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb (find), resource (journals), and the exact mechanism/source: matching an abstract against recent papers in OpenAlex. An agent can immediately distinguish this from search_papers or find_datasets without opening any schema.

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 triggering context ('to submit a manuscript'), input guidance ('paste the abstract, or title and abstract'), and a fallback instruction for non-English abstracts via `keywords`. It also sets a firm exclusion ('Quartiles are NOT included and must not be stated from memory'), but names no sibling alternative for the case where journal-finding is the wrong tool.

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.