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

io.github.xngg1021/academic-research-kernel

by xngg1021

academic_check_percentage

Verify whether a reported percentage and count can mathematically arise from a given sample size. Detects impossible or rounded statistics in research data before you cite them.

Instructions

Check if a reported percentage and count can mathematically arise from a sample size.

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": {
      "count": "<count>",
      "percent": "<percent>"
    },
    "name": "academic_check_percentage"
  }
}

Input Schema

NameRequiredDescriptionDefault
countYesObserved count (numerator)
percentYesReported percentage (e.g. 12.5)
sample_sizeNoOptional total sample size (denominator)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavioral burden and does not meet it. It does not say what a result looks like (boolean verdict, list of feasible sample sizes, rounding tolerance), whether percentages with decimal rounding are accommodated, or how the optional denominator alters behavior. Only the bare purpose is disclosed.

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?

A single front-loaded sentence with no filler, and the core predicate is stated immediately. It is efficient, though the terseness is partly the cause of the guidance gaps noted elsewhere rather than a virtue in itself.

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

Completeness3/5

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

For a small, single-purpose arithmetic check with a fully documented schema, the definition is minimally sufficient. However, given no output schema and no annotations, the description should at least characterize the verdict returned and the effect of omitting sample_size.

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

Parameters3/5

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

Schema description coverage is 100%, so count, percent, and sample_size are already labeled as numerator, reported percentage, and optional denominator. The description adds no format, rounding, or tolerance detail beyond the schema, so the baseline of 3 applies.

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 names a specific verb ("Check") and a precise resource: the mathematical consistency of a reported percentage and count against a sample size. That is far more informative than the tool name alone and is distinguishable from statistical siblings like academic_recompute_statistics. It stops short of explicitly contrasting itself with those siblings, so a 5 is not warranted.

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 guidance on when to use this versus alternatives such as academic_recompute_statistics or academic_table_forensics, nor on prerequisites. Critically, sample_size is optional, and the description never says what changes when it is omitted (e.g., whether the tool then enumerates plausible denominators). The caller must infer the two operating modes.

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