Skip to main content
Glama

Metis · News Radar — Scan Library

scan_library

Fetches journal and preprint feeds to add new papers to your Library, deduplicating by URL for literature alerts.

Instructions

Fetch the literature feeds and add new papers to the Library.

This is the Library's own scan: journal tables-of-contents and preprint
servers (Lancet ID, CDC EID, BMC Infectious Diseases, PLOS Medicine, Nature,
Science, medRxiv, arXiv …, plus any field journals configured locally),
written to `new_publications` for the literature-alert surface.

Separate from `scan_news` on purpose: this builds a scientific background
rather than reporting what happened, so it runs on its own schedule and its
output never appears on the News surface. Deduplicates by URL.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

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. It usefully discloses the write target (`new_publications`), the dedup rule (by URL), and the isolation from the News surface, but says nothing about network/auth requirements, runtime cost, or what happens on partial feed failure — meaningful gaps for a mutating fetch tool.

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

Conciseness4/5

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

Front-loaded with the core action and destination, then the sibling differentiation. The parenthetical feed list is somewhat long but conveys concrete scope; no sentence is empty filler.

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?

Output schema exists, so return values need not be explained, and with no inputs the description covers what an agent needs to decide and call. The remaining gap is distinguishing this from the several other literature-scan tools in the sibling set.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain; the description correctly spends no space on inputs and instead describes sources and output destination.

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?

States a specific verb+resource ('Fetch the literature feeds and add new papers to the Library') and names concrete source feeds plus the write target (`new_publications`). It distinguishes itself from `scan_news`, but not from other literature-scanning siblings such as `scan_literature`, `scan_pubmed_alerts`, or `scan_openalex`, which remain ambiguous alternatives.

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?

Gives a clear when-to-use context (builds a scientific background, runs on its own schedule) and an explicit exclusion (output never appears on the News surface). It does not say when to prefer this over `scan_literature`/`scan_pubmed_alerts`/`scan_openalex`, leaving the main routing ambiguity unresolved.

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

Deploy Server

Other Tools