Skip to main content
Glama
Sign In
Paper Fact Check

Paper Fact Check

by Biajin-PKU
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

render_report

Rebuilds report.html and report.md in a target directory, merging review.json data such as dismissals, edits and reviewer findings when present.

Instructions

Rebuild report.html and report.md in out_dir, merging review.json (dismissals, edits, reviewer findings, guideline items) if present.

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": {
      "out_dir": "<out_dir>"
    },
    "name": "render_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
out_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.3/5.0
Behavior2/5

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

There are no annotations, so the description carries the full behavioral burden. It discloses that it rebuilds two output files and conditionally merges review.json, but it does not state overwrite behavior, whether missing files are created, error conditions, permission requirements, or return behavior.

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?

The description is a single front-loaded sentence with no filler. It states the outputs, location, and conditional merge source efficiently.

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 one-parameter file-writing tool with no annotations or output schema, the description covers the main effect and merge source. However, important behavioral details about overwriting, failure modes, and output results are missing.

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 0%, but the description adds that out_dir is the directory where both report files are written. It does not clarify path format, whether the directory must already exist, or other parameter constraints.

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 ("Rebuild") and specific resources ("report.html and report.md in out_dir"), so the tool's core purpose is clear. It does not explicitly distinguish this from the sibling tool check_paper, which keeps it below a 5.

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?

The description implies usage when reports need rebuilding and review.json may need to be merged, but it does not state explicit when-to-use or when-not-to-use guidance. No alternatives or preconditions are named.

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

Deploy Server

Other Tools