Skip to main content
Glama

Plos Article

plos_article
Read-onlyIdempotent

Fetch a single PLOS article record by DOI (e.g. 10.1371/journal.pone.0153207), returning title, authors, publication date, journal, and abstract.

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": {
      "doi": "10.1371/journal.pone.0153207"
    },
    "name": "plos_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
doiYese.g. "10.1371/journal.pone.0153207"

Output Schema

NameRequiredDescriptionDefault
responseNo
responseHeaderNoResponse metadata from Solr

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds the shape of the returned record, which is helpful context but partially redundant given an output schema exists; it says nothing about rate limits, auth, or not-found behavior.

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?

A single well-formed sentence with the action and identifier front-loaded and the return payload trailing. No filler or redundant clauses.

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 one-parameter lookup with rich annotations and an output schema, this is close to complete. The only gap is error/empty-result behavior for an invalid or unknown DOI, which the description leaves to the schema and annotations.

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?

There is exactly one parameter with 100% schema coverage and a worked example in both the schema and the description. The description only repeats the DOI example format the schema already supplies, so it adds no new meaning — baseline 3.

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

Purpose4/5

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

The description names a specific verb and resource — 'Fetch a single PLOS article record by DOI' — and enumerates the returned fields (title, authors, publication date, journal, abstract). 'Single ... by DOI' implicitly distinguishes it from the sibling list/search tools, but no sibling is named explicitly.

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?

Usage is implied: call this when you already hold a DOI for one specific paper. There is no explicit statement of when to prefer plos_search or plos_recent instead, and no note on what happens if the DOI is unknown or malformed.

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.