Skip to main content
Glama

Quill Scholar Research Desk

Search papers (free)

search_papers
Read-only

FREE. Find papers on arXiv and Crossref by keywords: title, first authors, year, venue, DOI / arXiv id, link and citation count, up to 10 results. For a full reading list with synthesis use literature_review.

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": {
      "query": "<query>"
    },
    "name": "search_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoNumber of results (default 8)
queryYesKeywords or a paper title, e.g. "retrieval-augmented generation evaluation"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the cost signal ("FREE"), the external sources queried, and the hard cap of 10 results per call. It does not cover rate limits, failure behavior when a source is unreachable, or result ordering, which keeps it below a 5.

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?

Two sentences, no filler. The cost qualifier is front-loaded, followed by capability and returned fields, with the disambiguation sentence last where it is most useful for routing.

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?

For a two-parameter read-only search with no output schema, the description covers cost, sources, result cap, and the returned field set, which is everything an agent needs to call it and interpret the response. The sibling pointer closes the remaining routing question.

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 description coverage is 100%, so both parameters are already documented, and the description's "up to 10 results" merely restates the schema maximum. It adds the useful hint that the query may be either keywords or a paper title, but no further syntax or semantics.

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?

"Find papers on arXiv and Crossref by keywords" gives a specific verb, resource, and the two sources queried, then enumerates the returned fields (title, first authors, year, venue, DOI/arXiv id, link, citation count). It explicitly names the sibling it is not (literature_review), so an agent can route correctly without opening either 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 provides an explicit alternative and the condition that selects it: "For a full reading list with synthesis use literature_review." That is a clear when-to-use-else signal, though it does not state any when-not conditions for this tool itself (e.g. empty or ambiguous queries).

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