Skip to main content
Glama
Literature Evidence MCP

Literature Evidence MCP

by Furox-Art

expand_citation_chain

Bounded OpenAlex citation links, forward/backward; edges remain unverified metadata.

Instructions

Bounded OpenAlex citation links, forward/backward; edges remain unverified metadata.

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": {
      "seed_doi": "<seed_doi>"
    },
    "name": "expand_citation_chain"
  }
}

Input Schema

NameRequiredDescriptionDefault
seed_doiYes
max_depthNo
directionsNoboth
max_per_directionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

C2.7/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 that traversal is bounded and that edges are unverified metadata, but it omits read-only status, permissions or rate limits, and what the response contains.

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?

The description is extremely concise and front-loaded, with no wasted words. The single fragment structure is efficient but leaves important operational details implicit.

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

Completeness2/5

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

Given four parameters, no annotations, 0% schema coverage, and no output schema, the description is far too sparse. It does not explain the seed DOI, traversal depth, per-direction limits, or return shape, so an agent cannot call it confidently without opening the schema.

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

Parameters2/5

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

Schema description coverage is 0%, and the description names none of the four parameters explicitly. 'Forward/backward' loosely maps to directions and 'bounded' to the max limits, but seed_doi and the exact semantics of max_depth versus max_per_direction are undocumented.

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 description identifies OpenAlex citation links and forward/backward scope, but it is a noun phrase without an explicit operation or mention of the seed DOI. It partially differentiates from verify_citation by noting that edges are unverified, but the agent must infer that the tool expands a citation chain.

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 explicit when-to-use guidance, prerequisites, or named alternatives. 'Bounded' and 'unverified metadata' hint that this is exploratory rather than verification, but that routing signal is not stated directly.

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