Skip to main content
Glama

PaperList

List research topics

list_topics
Read-onlyIdempotent

List the 207 research topics that have trend stats, grouped into 40 areas, each with its slug, English and Chinese name, and paper count. Scope: NeurIPS, ICLR, ICML and CVPR, 2023–2026. Use a slug from here with get_topic_stats.

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": "list_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint, idempotent, non-destructive, closed-world), so the description's job is to add context — and it does: the fixed size (207 topics / 40 areas), the conference and year boundaries of the data, and the fields returned. It doesn't mention pagination or whether the list is stable across calls, but idempotentHint already implies stability.

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?

Three short sentences, front-loaded with the verb and scale, then scope, then the next-step pointer. No filler, and every clause carries information an agent would otherwise have to guess.

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?

Although an output schema exists and return details are therefore optional, the description still gives the agent enough to decide this tool is the right entry point before calling get_topic_stats. Nothing needed to invoke a no-argument listing correctly is missing.

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?

With zero input parameters there is no parameter meaning to convey; the description correctly spends no words on inputs and instead explains what the caller gets back. Baseline 4 for a no-parameter tool is appropriate.

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?

The description names a specific verb and resource ('List the 207 research topics'), and quantifies the shape of the result: 40 areas, each with slug, English and Chinese name, and paper count. It also pins the corpus scope (NeurIPS, ICLR, ICML, CVPR, 2023–2026), so an agent knows exactly what universe this listing covers without opening the schema.

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?

It explicitly routes the agent forward: 'Use a slug from here with get_topic_stats,' naming the sibling and the dependency between them. It doesn't state when-not to use it (e.g., versus search or list_conferences), but the tool's role as a slug-discovery step is unambiguous.

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