Skip to main content
Glama
Literature Evidence MCP

Literature Evidence MCP

by Furox-Art

record_risk_of_bias

Record two human RoB2/ROBINS-I V2 Nov-2025 appraisals, flag disagreements.

Instructions

Record two human RoB2/ROBINS-I V2 Nov-2025 appraisals, flag disagreements.

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": {
      "framework": "<framework>",
      "study_id": "<study_id>",
      "outcome": "<outcome>",
      "reviewers": "<reviewers>"
    },
    "name": "record_risk_of_bias"
  }
}

Input Schema

NameRequiredDescriptionDefault
outcomeYes
study_idYes
frameworkYes
reviewersYes
effect_of_interestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.5.1

TDQS

C2.7/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 behavioral burden. It reveals that two human appraisals are recorded and disagreements are flagged, but omits mutation behavior such as overwrite rules, validation, permissions, error handling, 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.

Conciseness5/5

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

A single front-loaded sentence with no wasted words. It efficiently states the core action, the dual-appraisal requirement, and the disagreement behavior.

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?

The tool has five parameters including a nested reviewers array, no annotations, no output schema, and zero schema description coverage. A one-sentence description is far too thin to tell an agent how to construct valid reviewer objects or understand the operation's full behavior.

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%, so the description must compensate and mostly does not. It implies framework values (RoB2/ROBINS-I V2) and that reviewers must be two humans, but does not explain study_id, outcome, effect_of_interest, or the nested reviewer object shape.

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 and resource: recording RoB2/ROBINS-I V2 risk-of-bias appraisals. It also specifies the dual-reviewer context and disagreement flagging, which distinguishes it from siblings like assess_methodology or audit_methodology, though it does not explicitly name alternatives.

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?

The description implies this is used to record two human appraisals, but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not explain when to choose this over assess_methodology or record_grade.

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