Skip to main content
Glama
Sign In

AgingResearch.News

by news.agingresearch
OverviewDiscussionsAdmin

Get a paper

get_paper
Read-onlyIdempotent

Use this when the user wants one paper in depth: what it did and found, in which species and how many subjects, its caveats, who wrote it and where they work. Takes a paper id such as MED-42823970 from another tool's results, or the paper's own DOI, PMID, PMCID, arXiv id or a link to it. Returns how it bears on aging, the language it was published in with its own-language title when that is not English, every author with ORCID iD and institutions, its full story (headline, body, why it matters, caveats) when published, the drugs, genes and processes it studies and its findings, and a link to the paper at its source. It does not replace the paper.

Input Schema

NameRequiredDescriptionDefault
idYesPaper id (MED-42823970), or the paper's DOI (10.1038/…, doi:10.1038/…, https://doi.org/10.1038/…), PMID (42823970, PMID:42823970), PMCID (PMC1234567), arXiv id (2610.02175), or a link to it on AgingResearch.News, PubMed, PMC, Europe PMC, arXiv, bioRxiv or a publisher's page with its DOI.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Paper id, e.g. MED-42823970."New value: +"Paper id (MED-42823970), or the paper's DOI (10.1038/…, doi:10.1038/…, https://doi.org/10.1038/…), PMID (42823970, PMID:42823970), PMCID (PMC1234567), arXiv id (2610.02175), or a link to it on AgingResearch.News, PubMed, PMC, Europe PMC, arXiv, bioRxiv or a publisher's page with its DOI."
  2. Changed1 schema field changed
    • changedInput schema / properties / id / maxLength
      Previous value: -80New value: +200
  3. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"ARN paper id, e.g. MED-42823970."New value: +"Paper id, e.g. MED-42823970."
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare this as a safe, read-only, idempotent operation, and the description adds substantial behavioral context: it explains what information is returned, including aging relevance, language and title handling, author details, paper story, studied entities, findings, and a source link. It also clarifies that it does not replace the paper itself.

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 front-loaded with the usage condition, followed by input and return details. Despite being fairly rich, every sentence serves a purpose by clarifying when to use it, what input it accepts, and what the agent should expect back.

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

Completeness5/5

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

There is no output schema, so the description must carry the return-value burden, and it does so thoroughly. Combined with annotations that cover safety and idempotency, the definition gives an agent enough context to select and invoke the tool correctly.

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%, and the schema already documents the accepted id formats in detail. The description reinforces that the id can come from another tool's results or be a DOI, PMID, PMCID, arXiv id, or link, but it does not add syntax or semantics beyond the schema.

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 uses a specific verb and resource: it tells the agent this tool retrieves one paper in depth. It clearly distinguishes the tool from list/search tools by emphasizing a single paper and its full details, so an agent can identify it without opening the 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?

It gives a clear usage condition: 'when the user wants one paper in depth.' It also explains accepted identifiers, including ids from other tools and standard paper identifiers. It does not explicitly name alternatives like list_papers or search_papers, but the single-paper scoping makes the intended use clear.

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

All AgingResearch.News toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources