journal-scout-mcp

get_paper

Resolve a scholarly paper identifier across sources, merge metadata, and obtain open-access links.

Instructions

Resolve a DOI/arXiv/Scopus/OpenAlex id across sources, merge metadata, and attach open-access links.

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": {
      "identifier": "<identifier>"
    },
    "name": "get_paper"
  }
}

Input Schema

Name	Required	Description	Default
`identifier`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Sep 25, 2026

TDQS

A3.8/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 of behavioral disclosure. It mentions merging metadata and attaching open-access links, which is useful, but it does not describe error handling, response format, or confirm the operation is read-only. The description is adequate but not comprehensive.

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?

The description is a single, well-structured sentence that front-loads the action and resource. Every word adds value, and it is concise without sacrificing needed 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?

For a tool with one parameter and no output schema, the description covers the main purpose and accepted input types. It is close to complete, though it could benefit from specifying the return format or behavior when an identifier cannot be resolved. Given the simplicity and lack of annotations, it is adequately complete.

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?

The schema has 0% description coverage, so the description must compensate. It lists the accepted identifier types (DOI/arXiv/Scopus/OpenAlex), giving meaning beyond the bare 'string' type. However, it omits format specifics and does not clarify which identifiers are prioritized or how they are combined, so it only partially compensates.

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?

The description states a specific verb ('resolve') with a clear resource (DOI/arXiv/Scopus/OpenAlex id) and the intended outcome (merge metadata, attach open-access links). It clearly distinguishes itself from the search sibling tools by focusing on resolving an existing identifier rather than searching.

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 description implies the tool is for when you have an existing identifier, but it does not explicitly contrast with the many search_* siblings or state when not to use it. It lacks guidance on alternatives or conditions for selection, leaving usage to inference.

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

Deploy Server