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

io.github.xngg1021/academic-research-kernel

by xngg1021

academic_pre_submission_lint

Audit a LaTeX manuscript against venue formatting, section, double-blind, and statistical-dispersion rules before submission, optionally checking claim-evidence bindings and academic prose style.

Instructions

Audit a LaTeX manuscript against venue formatting rules, required sections, double-blind package options, statistical dispersion, CEG claim bindings, and optional academic prose style checks.

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": {
      "tex_path": "<tex_path>"
    },
    "name": "academic_pre_submission_lint"
  }
}

Input Schema

NameRequiredDescriptionDefault
phaseNoSubmission phase, default submission
venueNoTarget venue key, default iclr
ceg_pathNoOptional ClaimEvidenceGraph JSON path
pdf_pathNoOptional compiled PDF path for page-limit verification
tex_pathYesPath to main .tex entry file or manuscript directory
contribution_typeNoContribution type key, default general_empirical
require_ceg_bindingNoFlag quantitative claims in Abstract/Conclusion without verified CEG binding
check_academic_styleNoEmit advisory hits for academic LLM cliches, unanchored strong claims, and vague passive methods

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does useful work by naming the check categories that will run, but it never states that the operation is read-only, whether any files or a sanitized package are written, how findings are severity-ranked vs. hard failures, or what a call returns despite there being no output schema.

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?

It is a single front-loaded sentence with no filler, and the verb-plus-resource leads. The trailing enumeration is long but each item names a distinct check surface, so it earns its length; a short structural break would improve scanability.

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 an eight-parameter tool with no annotations and no output schema, the description covers what is inspected but omits what comes back (report format, pass/fail semantics, whether a linter exit is advisory or blocking) and how it relates to the narrower sibling tools. An agent could call it, but could not predict the result shape.

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 all eight parameters are already documented in the schema, making 3 the baseline. The description adds little parameter-level meaning beyond implying that venue and phase shape the rule set, and it does not explain the interaction between require_ceg_binding/ceg_path or what contribution_type changes.

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 ("Audit a LaTeX manuscript") and enumerates the concrete check families it covers: venue formatting rules, required sections, double-blind packaging, statistical dispersion, CEG claim bindings, and prose style. That is far more specific than a restatement of the name. It does not, however, distinguish the aggregate audit from overlapping siblings such as academic_double_blind_sanitize or academic_check_percentage.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the tool name and the word "pre-submission" — an agent can infer this is the umbrella check to run before submitting. There is no explicit statement of when to run this versus calling the narrower sibling tools (double-blind sanitize, percentage check, source verify) first, and no prerequisites or exclusions are given.

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