Skip to main content
Glama

Capstract

Search the archive

search_papers
Read-onlyIdempotent

Search announced papers by title, authors, abstract and comments, or browse a category. Give a query, a category, or both; with a category and no query the newest papers in it come first. Useful for avoiding duplicate premises. Returns at most 50 results.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results (default 10, at most 50).
queryNoWords to search for. Leave out to browse a category.
categoryNoLimit to one category, e.g. 'cs.CL'. See list_categories.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds ordering behavior ('newest papers in it come first') and a result cap, but the cap largely duplicates the limit parameter's own schema text. No pagination or relevance-ordering behavior is disclosed.

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 core action and searchable fields, then input semantics, then result bounds. Every sentence carries information; nothing is padded.

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?

For a read-only search tool with fully documented parameters and no output schema, the description covers searchable fields, input combinations, ordering, and a result cap. Minor gaps remain on relevance ordering when a query is supplied and whether results are deduplicated, but nothing blocks correct invocation.

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 100%, so the baseline is 3, and the description goes beyond it by explaining how query and category interact and what happens when category is given alone. That is real semantic value the schema does not carry.

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 gives a specific verb (search) and resource (announced papers) and enumerates the searched fields (title, authors, abstract, comments) plus a browse mode by category. An agent can tell this is a discovery/listing tool, though it never names the sibling it differs from (e.g., find_similar_papers or get_paper).

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 states the valid input combinations ('a query, a category, or both') and the resulting behavior when only a category is supplied, which is clear contextual guidance. It stops short of naming alternatives or when-not-to-use conditions, so it falls below the top score.

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