Skip to main content
Glama
io.github.xngg1021/academic-research-kernel

io.github.xngg1021/academic-research-kernel

by xngg1021

academic_meta_analyze

Run deterministic fixed-effect and DerSimonian-Laird random-effects meta-analysis with heterogeneity statistics, leave-one-out sensitivity, Egger regression, and trim-and-fill to synthesize effect sizes across studies.

Instructions

Run deterministic fixed-effect and DerSimonian-Laird random-effects meta-analysis, heterogeneity (Q, I2, tau2), leave-one-out sensitivity, Egger regression, and Duval-Tweedie trim-and-fill.

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": {
      "studies": "<studies>"
    },
    "name": "academic_meta_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
studiesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 does disclose one real behavioral trait — 'deterministic' — and its enumeration of Q, I2, tau2 hints at what is returned despite there being no output schema. It says nothing about failure modes (e.g., a single study, as minItems:1 permits, cannot support heterogeneity or Egger regression), no confidence-interval or p-value reporting, and no note that Egger/trim-and-fill are unreliable at small k.

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?

One dense, front-loaded sentence with no filler — every clause names a distinct computation. The trade-off is that the method list is a comma run-on, but nothing is redundant.

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?

For a statistically complex tool with no annotations, no output schema, and a nested-object input, the definition is incomplete: the agent cannot learn the shape of the result, the minimum study count needed for each diagnostic, or how degenerate inputs are handled. The method list describes inputs-to-computations but not outcomes or constraints.

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% at the top level, so the description should compensate, but it never mentions the sole parameter. It does not explain that each study requires an effect size yi and a positive within-study variance vi, nor does it warn that the diagnostic methods it advertises require more than the single study the schema permits.

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 description opens with a specific verb and resource ('Run ... meta-analysis') and enumerates exactly which estimators and diagnostics are computed (fixed-effect, DerSimonian-Laird, Q/I2/tau2, leave-one-out, Egger, trim-and-fill). That is far more specific than the sibling academic_* names, though it never explicitly contrasts itself with academic_recompute_statistics or similar tools.

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 or when-not-to-use guidance, no statement of prerequisites (e.g., effect sizes must be on a comparable scale, variances must be within-study sampling variances), and no routing to or away from sibling tools. The only usage signal is implicit in the tool name and the method list.

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