AI-Scholarly-Mode

get_articles_list

Retrieve a list of peer-reviewed academic articles from Springer Nature's open access collection using a search query.

Instructions

Get articles list

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": {
      "query": "<query>"
    },
    "name": "get_articles_list"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes
`articles_per_page`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 30, 2026

TDQS

D1.3/5.0

Behavior1/5

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

No annotations are provided, so the description must fully disclose behavioral traits. It fails to mention whether the operation is read-only, destructive, or what the output format is. The agent has no information about side effects, rate limits, or authorization needs.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise but achieves this at the cost of all informative content. Under-specification is not conciseness; every sentence should earn its place, and here there is only a single tautological phrase.

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

Completeness1/5

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

Given the tool has two parameters, no output schema, and no annotations, the description is woefully incomplete. An agent cannot determine the return format, pagination behavior, or how to form a valid query. The description fills none of the gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description adds no information about the parameters. 'query' is unexplained (e.g., search syntax, fields) and 'articles_per_page' lacks constraints (e.g., min, max, default). The description adds zero value beyond the bare schema names.

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

Purpose1/5

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

Description 'Get articles list' is a tautology that merely restates the tool name. It does not specify the source, type, or criteria for articles, and fails to distinguish from the sibling tool 'get_springer_article_data' which likely provides article data from a specific source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidelines provided. The description does not indicate when to use this tool versus alternatives like 'get_springer_article_data' or the scholarly mode tools. The agent receives no context about prerequisites or appropriate scenarios.

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

Deploy Server