Skip to main content
Glama

PaperList

Find similar papers

find_similar_papers
Read-onlyIdempotent

Find papers related to a given paper, ranked by full-text similarity of its title and keywords. Defaults to slim rows; pass fields=full for abstracts. Optionally restrict to conferences or years.

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": {
      "id": "<id>"
    },
    "name": "find_similar_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPaper id from search results
limitNoResults per page. slim: search up to 200 (default 10), list_papers up to 250 (default 100). full: 1-25 (default 10).
cursorNonext_cursor from a previous call
fieldsNoslim (default for list_papers/search_papers/find_similar_papers) returns id, title, conference, year, decision, rating_avg, url, and short topics. Use full or get_paper/fetch for abstracts. Prefer slim when scanning or exporting a conference.
year_toNo
year_fromNo
conferencesNoConference slugs from list_conferences, e.g. ["iclr", "neurips"]

Output Schema

NameRequiredDescriptionDefault
noteNo
yearNo
totalNo
fieldsNo
papersYes
conferenceNo
next_cursorYesPass as cursor to get the next page; null when there are no more results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world corpus, so the safety profile is covered. The description adds genuinely new behavior: ranking is by full-text similarity of title and keywords, and rows default to slim with fields=full needed for abstracts. It says nothing about ranking tie-breaks or result-set size behavior beyond the schema.

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 purpose and ranking method, followed by output-projection and filtering notes. No filler, no restatement of the title.

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 return shapes needn't be described, and the description covers the non-obvious pieces: similarity ranking, slim default, and optional conference/year narrowing. Pagination behavior (cursor, per-mode limits) is left entirely to the schema, which is acceptable given the output schema and annotation coverage.

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 71%, so the schema does most of the work and a baseline of 3 applies. The description reinforces the fields=slim/full tradeoff and the conference/year filters, but adds no detail beyond the schema's own parameter descriptions (e.g., how year_from/year_to are inclusive or what cursor semantics are).

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?

States a specific verb and resource ("Find papers related to a given paper") plus the ranking basis (full-text similarity of title and keywords), which is real information beyond the name. It does not distinguish itself from siblings like search_papers or get_paper, so an agent must infer that this is the similarity/nearest-neighbor route.

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

Usage Guidelines3/5

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

Implies usage through "related to a given paper" and notes optional conference/year restrictions, but never says when to prefer it over search_papers or get_paper, nor when-not to use it. Anyone reaching for keyword search instead would get no routing signal from this text.

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