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

io.github.xngg1021/academic-research-kernel

by xngg1021

academic_openreview_audit

Audit OpenReview submission status, ratings, and review word counts from offline notes, or compute venue acceptance and rating distributions from mirror records.

Instructions

Audit OpenReview submission status, ratings, review word counts, or macro venue acceptance/rating distributions from offline notes or mirror records.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "academic_openreview_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoOptional offline OpenReview notes list for single-paper audit
forum_idNoOpenReview forum ID
topic_regexNoOptional regex filter for venue_records
venue_recordsNoOptional venue mirror records list for macro statistics

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/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. It does disclose something valuable: the audit runs against offline notes or mirror records, so no live OpenReview fetch occurs. But it says nothing about read-only vs mutating behavior, what happens when both or neither input collection is supplied, error conditions, or output shape, which is a significant gap for an unannotated 4-parameter tool.

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 sentence with the verb front-loaded and no filler; the enumerated audit targets are dense but each item carries information. The one weakness is that the list of metrics crowds out the operational detail the tool actually needs.

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 tool with no output schema and no annotations, the description should explain what comes back and how the two optional input modes behave. It names the computed metrics, which partially covers the return side, but leaves the interaction between notes and venue_records, and the no-argument case, entirely unexplained.

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 100%, so the schema already documents each parameter's role, including the single-paper vs macro-statistics split. The description mostly restates the fields it audits and adds no syntax, precedence, or format detail beyond what the schema provides, leaving it at the baseline rather than above it.

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 (Audit) and enumerates the concrete outputs: submission status, ratings, review word counts, and venue acceptance/rating distributions. That is far more specific than a tautology, though it does not name or contrast any sibling tool, so an agent must infer that this is the OpenReview-specific option among the academic_* utilities.

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 phrase 'from offline notes or mirror records' implies the usage context: the tool works on data you supply rather than a live service. However, there is no explicit when-to-use/when-not guidance, no mention of alternatives, and no direction on which input set to choose, even though all four parameters are optional and a call with no arguments is schema-valid.

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