Lune Research

Get conference papers

get_conference_papers

Read-onlyIdempotent

Use this when the user asks for papers from a specific conference (optionally a year), e.g. “most-cited NeurIPS 2024 papers”, “show me CCS 2025 accepted papers”, or “what's new in security at IEEE S&P this year”. sort is recency (newest first, default) or citations (most-cited first); page with limit / offset.

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": {
      "conference": "<conference>"
    },
    "name": "get_conference_papers"
  }
}

Input Schema

Name	Required	Description	Default
`sort`	No	`recency` (newest first, default) or `citations` (most-cited first).	recency
`year`	No	Restrict to a single year (e.g. 2024). Omit to span all years.
`limit`	No	Max papers to return per page (default 20, max 100).
`offset`	No	Pagination offset; use to fetch subsequent pages.
`conference`	Yes	Conference short name, e.g. "NeurIPS", "CCS", "ICLR".

Output Schema

Name	Required	Description
`total`	No	Total papers at this venue matching the filters (paging count).
`papers`	Yes
`has_more`	No	True when more papers exist past this page; re-call with offset += limit.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavior: default ordering is newest-first and results are paginated via limit/offset, which the agent needs to reason about paging through results. It omits what happens on an unrecognized conference name or whether an empty result is possible.

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?

A single dense paragraph that front-loads the usage trigger before the example queries and the sort/pagination mechanics. Every clause carries information an agent needs; nothing is filler.

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 an output schema present and full schema descriptions, the description needn't explain return values, and it covers the trigger plus ordering and paging. It leaves a small gap around conference-name validity, notable given a sibling list_conferences exists that could resolve canonical names.

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

Parameters3/5

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

Schema coverage is 100%, so every parameter is already documented, including the sort enum and its default. The description restates the sort values and the limit/offset pairing but adds no syntax, format or matching rules beyond the schema, such as whether conference must match a canonical short name.

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?

The description names the resource (papers) and its scope (a specific conference, optionally a year) and frames it as a retrieval operation, so an agent can tell it apart from generic search_papers. It stops short of explicitly naming the sibling it replaces, relying on the scenario rather than a direct contrast.

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 gives a concrete when-to-use trigger ("when the user asks for papers from a specific conference") plus three realistic example queries that include conference and year phrasing. It offers no when-not guidance or explicit alternative (e.g., "use search_papers for cross-conference keyword search").

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

All Lune Research tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.