Skip to main content
Glama

Plos Recent

plos_recent
Read-onlyIdempotent

Most recent publications across PLOS.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rows": 25
    },
    "name": "plos_recent"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsNo

Output Schema

NameRequiredDescriptionDefault
responseNo
responseHeaderNoResponse metadata from Solr

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds nothing beyond that — no ordering, freshness window, default result count, or rate/pagination behavior for an open-world remote source. With rich annotations the bar is lower, but there is still zero added context.

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

Conciseness3/5

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

One sentence with no filler and no repetition, which is good, but the brevity is under-specification rather than efficiency — the front-loaded phrase "Most recent publications" is followed by nothing actionable.

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

Completeness2/5

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

This is a simple tool with one optional parameter and an output schema, so return values need no explanation. Still, the description omits what "recent" means (a time window, a fixed count) and what `rows` controls, leaving the agent without enough to call it with confidence.

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

Parameters2/5

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

The single parameter `rows` has 0% schema description coverage and is never mentioned in the description, so its meaning (count of results, default value, maximum) and the fact that it is optional are left entirely to inference. The description does not compensate for the coverage gap.

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

Purpose3/5

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

"Most recent publications across PLOS" identifies the resource (publications) and the scope (most recent, PLOS-wide), so an agent can infer a recency-ordered listing. However, there is no explicit verb and nothing distinguishes it from siblings like plos_search or plos_article, which plausibly overlap on the same corpus.

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?

There is no when-to-use guidance at all: no statement of when to prefer this over plos_search or plos_article, no mention of whether it is scoped to a subject, journal, or date window, and no exclusions. The agent must guess based on the name alone.

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.