Skip to main content
Glama
Literature Evidence MCP

Literature Evidence MCP

by Furox-Art

prisma_review_flow

Auditable PRISMA identification/screening and explicit missing full-text stages.

Instructions

Auditable PRISMA identification/screening and explicit missing full-text stages.

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": {
      "identified": "<identified>",
      "records": "<records>",
      "checklist": "<checklist>"
    },
    "name": "prisma_review_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
recordsYes
checklistYes
identifiedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

D1.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, yet 'auditable' and 'missing full-text stages' are the only behavioral hints — there is no disclosure of whether records are persisted, whether the output is a computed PRISMA count table, what validation the checklist enforces, or what the response contains. The 'missing full-text stages' phrase is a genuinely useful scope disclosure, which is why this is not a 1.

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

Conciseness2/5

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

A single eleven-word fragment is not conciseness but under-specification; nothing is front-loaded because nothing is explained. There is no wasted word, but the text is far below the minimum needed for a three-nested-parameter tool.

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?

With no annotations, no output schema, three fully undocumented required nested parameters, and several closely related PRISMA/evidence siblings, the description omits everything an agent needs to call this correctly. It is not adequate for the tool's complexity.

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?

Three required parameters (identified, records, checklist) with 0% schema description coverage and nested object types, and the description says nothing about any of them — not the expected shape of 'identified' versus 'records', nor what keys 'checklist' must contain. The agent has essentially no way to construct valid arguments from the definition alone.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description is a noun phrase ('Auditable PRISMA identification/screening and explicit missing full-text stages') rather than a verb+resource statement, so it never says what the tool actually does — build a flow diagram, record counts, or log screening decisions. It adds a few keywords beyond the name (identification/screening stages, absent full-text stage) but remains a restatement of the tool's title concept rather than an action.

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 when-to-use, when-not-to-use, or prerequisite guidance at all, despite a directly overlapping sibling (prisma_dual_screen) that an agent could easily confuse this with. The phrase 'missing full-text stages' hints at a scope boundary but never says to use another tool instead.

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