Skip to main content
Glama

ICLR acceptance odds from review scores

iclr_acceptance_odds
Read-onlyIdempotent

Historical ICLR acceptance rate for papers with similar reviewer ratings, from public OpenReview decisions (kernel estimate over past score profiles). Give 3–6 ratings on the 0–10 scale ICLR used through 2026 (even numbers 0, 2, 4, 6, 8, 10; 2024–2025 used 1, 3, 5, 6, 8, 10). ICLR 2027 ratings are on a new 1–4 scale (clear reject, leaning reject, leaning accept, clear accept) with no acceptance history yet, so do not pass 2027 ratings here. Not a prediction of any decision.

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": {
      "scores": "<scores>"
    },
    "name": "iclr_acceptance_odds"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoReference year: 2026, 2025, 2024 (default: latest).
scoresYesReviewer ratings on the 0–10 scale (ICLR 2026 and earlier), e.g. [6, 6, 8, 4].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / scores / description
      Previous value: -"Reviewer ratings, e.g. [6, 6, 8, 4]."New value: +"Reviewer ratings on the 0–10 scale (ICLR 2026 and earlier), e.g. [6, 6, 8, 4]."
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered; the description goes further by disclosing data provenance (public OpenReview decisions), the statistical method (kernel estimate over past score profiles), the historical coverage window, and an explicit epistemic caveat that this is not a decision prediction. That is real behavioral context an agent cannot get from structured fields.

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?

Front-loaded with the core purpose, then the input requirement, then the important exclusion. Every sentence carries information, though the middle sentence packing two different historical rating scales is dense and takes a second read.

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

Completeness4/5

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

With no output schema, the description should ideally state what comes back (a percentage? a rate with confidence?). It conveys 'historical acceptance rate' clearly enough to infer a numeric result, and it covers inputs, exclusions, and interpretation caveats well, so the only material gap is return-value shape.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3, but the description earns above baseline by specifying the historically valid rating values per era (0,2,4,6,8,10 through 2026; 1,3,5,6,8,10 for 2024–2025) and clarifying that 2027 uses a different 1–4 scale. This adds scale-validity meaning beyond the plain 'number 0–10' schema constraint.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and computation: 'Historical ICLR acceptance rate for papers with similar reviewer ratings, from public OpenReview decisions (kernel estimate over past score profiles).' An agent can immediately distinguish this from siblings like convert_score or get_review_form, since it names the exact dataset and estimator used.

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

Usage Guidelines4/5

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

Gives clear input preconditions (provide 3–6 ratings) and an explicit exclusion: 2027 ratings on the new 1–4 scale have no acceptance history, so 'do not pass 2027 ratings here.' It also manages expectations with 'Not a prediction of any decision.' It stops short of naming which sibling to use for 2027 ratings (e.g., convert_score), so it is strong but not fully routable.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources