Skip to main content
Glama
Literature Evidence MCP

Literature Evidence MCP

by Furox-Art

propagation_alerts

Source-linked correction/retraction alerts without treating citations as retractions.

Instructions

Source-linked correction/retraction alerts without treating citations as retractions.

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": {
      "nodes": "<nodes>",
      "edges": "<edges>",
      "notices": "<notices>"
    },
    "name": "propagation_alerts"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgesYes
nodesYes
noticesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

C2.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it discloses only one behavioral trait: citations are not treated as retractions. It says nothing about whether the tool reads or writes, what the alert output looks like, or how propagation is computed.

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?

A single clause with no filler is front-loaded, so it is concise, but it is under-specified for a three-object graph-shaped input. Brevity here costs more than it saves.

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

Completeness1/5

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

For a tool requiring three structured collections, with no annotations, no output schema, and zero parameter documentation, the description leaves essentially every question an agent would need answered before invoking it.

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

Parameters1/5

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

All three required parameters (nodes, edges, notices) are untyped generic objects at 0% schema coverage, and the description gives no hint of their expected shape, required fields, or how they relate — e.g. whether edges reference node ids or whether notices attach to sources.

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?

The phrase 'source-linked correction/retraction alerts' does gesture at a specific domain concept and adds the 'not citations' distinction, but there is no verb — an agent cannot tell whether this computes, lists, or emits alerts, nor how it differs from check_retraction or crossref_update_alerts.

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 stated condition for when to call this versus check_retraction, crossref_update_alerts, or verify_citation. The only implied guidance is the negative caveat about citations, which is not a usage rule.

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