Skip to main content
Glama

PaperList

List conferences

list_conferences
Read-onlyIdempotent

List conferences in Paperlist with their slugs, full names, research domains and available years, including ICLR 2027 (under-review submissions on the public ratings board). Pass topics_for {conference, year} to also get that edition's topic slugs with paper counts (use the slugs as the topic filter in search_papers/list_papers; ICLR 2027 areas are prefixed iclr2027-). No account or API key required.

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_conferences"
  }
}

Input Schema

NameRequiredDescriptionDefault
topics_forNo

Output Schema

NameRequiredDescriptionDefault
topicsNo
conferencesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds two genuinely new behavioral facts beyond that: no account or API key is required, and ICLR 2027 entries come from a public ratings board of under-review submissions. It does not discuss result size, ordering, pagination or failure behavior for an unknown conference slug.

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?

Three tight sentences, front-loaded with the primary action before covering the optional parameter and the auth note. The heavily parenthesized middle sentence packs the routing, prefix convention and response contents together, which is efficient but slightly dense on first 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?

An output schema exists, so the enumeration of returned fields is a bonus rather than a necessity, and the auth and cross-tool usage notes round out the picture for a single-parameter read tool. Completeness is only marginally short on the invalid-slug/edition edge case, which matters because the description advertises a fixed set of known editions.

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 coverage is 0%, so the description must carry the parameter, and it largely does: it names the optional object's two subfields, explains that topics_for switches the response to include topic slugs with paper counts, and gives the iclr2027- prefix convention for topic slugs. The residual gap is the year value's accepted domain — whether a year not in the listed editions is accepted, ignored or errors is left unstated, and the nested year property has no schema description.

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?

Opens with a specific verb+resource ("List conferences in Paperlist") and enumerates exactly what each entry carries: slugs, full names, research domains, available years. It also names the concrete coverage edge case (ICLR 2027 under-review) and positions itself in the workflow that feeds search_papers/list_papers, so an agent can separate it from list_topics or list_papers without opening a 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?

Gives a clear conditional for the optional parameter: "Pass topics_for {conference, year} to also get that edition's topic slugs" and states what to do with the returned slugs (use as the topic filter in search_papers/list_papers). What is missing is any explicit exclusion — nothing says when NOT to call this or when list_topics would be preferable — but the intended follow-on flow 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