Skip to main content
Glama

PaperList

Get topic stats

get_topic_stats
Read-onlyIdempotent

Trend stats for one research topic across NeurIPS, ICLR, ICML and CVPR, 2023–2026: paper counts by year × venue, year-over-year growth, fastest-growing co-labeled sub-themes, sibling topics in the same area, and ~20 representative papers (title, venue, year, paperlist id). Precomputed snapshot, no live aggregation. Get slugs from list_topics (e.g. world-models, multimodal-llms, reinforcement-learning). For ICLR 2027 primary areas, pass a slug from list_conferences topics_for {conference:"iclr", year:2027} (prefixed iclr2027-).

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": {
      "topic": "<topic>"
    },
    "name": "get_topic_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: 'Precomputed snapshot, no live aggregation,' which tells the agent results may be stale and are not recomputed on demand. It does not mention pagination or limits on the ~20 representative papers, which is a minor gap.

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 purpose and output contents, then prerequisites, then the special-case exception. Dense but every clause adds information; the enumerated result contents are somewhat verbose given an output schema exists.

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

Completeness5/5

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

Covers purpose, coverage window, venues, output contents, data freshness, and slug sourcing for both normal and ICLR 2027 cases. With an output schema present, the description adds all the invocation-time context needed for a single-parameter read tool.

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?

The single parameter has 0% schema description coverage, so the description carries the burden and does so well: it explains that the value is a slug, where to source it (list_topics), example values, and a prefixed variant for ICLR 2027 areas. It stops short of stating matching semantics such as case sensitivity or behavior on an unknown slug.

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 verb+resource (trend stats for one research topic) with explicit scope: four venues, 2023–2026, and the exact breakdowns returned. An agent can immediately distinguish this from search_papers or get_paper, which return individual papers rather than aggregated trends.

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

Usage Guidelines5/5

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

Explicitly routes the agent to list_topics to obtain valid slugs and names examples (world-models, multimodal-llms, reinforcement-learning). It also gives a conditional alternative for a specific case: ICLR 2027 primary areas require a slug from list_conferences topics_for with the iclr2027- prefix.

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