Skip to main content
Glama

Metis — Check For Newer Evidence

check_for_newer_evidence

Check how old your corpus is on a topic and find papers published since, via local recency report or optional PubMed and OpenAlex searches. Use it to spot superseded answers.

Instructions

How old is the corpus on this topic, and what has been published since?

The second half of fact-checking a quantity. A spread computed from a library
whose newest paper on the topic is from 2014 is a 2014 answer — possibly
correct, possibly superseded, and the corpus cannot tell you which because it
does not know what it lacks.

Recency is computed LOCALLY first and reported whether or not you go online,
because knowing how stale you are is what decides whether the search is worth
making. Set `search_online=True` to query PubMed and OpenAlex for work newer
than the corpus — metadata only, nothing of the researcher's is transmitted.

Anything returned from a search is ATTRIBUTED, not quoted: a title and a DOI
that nobody has read. Never present it beside a corpus passage as if the two
were the same kind of evidence, and use `verify_doi` before citing one.

Args:
    question: The question, e.g. "specificity of the RDT in community screening".
    search_online: Query PubMed + OpenAlex for newer work. Ask first.
    limit: Maximum results per source (default 8).

Returns:
    The corpus date range for this topic and, if requested, newer candidate
    sources with their years and DOIs.

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": {
      "question": "<question>"
    },
    "name": "check_for_newer_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
questionYes
search_onlineNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.5

TDQS

A4.4/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it states recency is computed locally and always reported, that online search transmits nothing of the researcher's, that results are metadata-only (title + DOI, unread), and warns against presenting them beside corpus passages as equivalent evidence. This is unusually rich behavioral framing for a read-only tool.

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?

The content is valuable but the opening is rhetorical framing ('How old is the corpus on this topic...') rather than a front-loaded statement of action, and the 2014/spread paragraph is discursive. Several sentences earn their place on behavior, but the definition could be trimmed by a third without losing instruction.

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?

The tool is a read-only computation with an output schema, and the description still explains what comes back (corpus date range, and if requested, candidate sources with years and DOIs). Combined with privacy and interpretation cautions, an agent has everything needed to call and use it correctly.

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

Parameters5/5

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

Schema coverage is 0%, so the description must compensate, and it does for all three parameters: `question` gets a concrete example, `search_online` gets both its effect and its side effect (which sources are queried), and `limit` is clarified as 'maximum results per source' with its default — meaning the schema alone would not convey.

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 second line ('The second half of fact-checking a quantity') plus the opening question make clear this computes corpus recency and optionally searches for newer work. It distinguishes itself from verify_doi by naming it as the follow-up step, though it never explicitly contrasts with siblings like search_literature or scan_openalex, which overlap in the online-search behavior.

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?

Explicit conditional guidance: recency is computed locally regardless, and `search_online=True` adds PubMed/OpenAlex lookup — plus a clear 'Ask first' instruction before making the online call. It also routes the agent to `verify_doi` before citing. It lacks a when-not-to-use statement (e.g., versus search_literature).

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