Skip to main content
Glama

search_papers

Search academic papers. Returns normalized hits with a short abstract preview; call get_paper for the full record.

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
queryYes
startNo
sourceNoarxiv
sort_byNorelevance
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral load. It does disclose that results are 'normalized hits with a short abstract preview' and that get_paper is needed for full records, which is meaningful output and workflow context. However, it says nothing about pagination via start/max_results, how source or sort_by affect behavior, rate limits, or what 'normalized' means, leaving significant behavioral gaps.

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 tightly written sentences, with the purpose front-loaded, followed by the return-preview behavior and the next-step routing. Every clause earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a five-parameter search tool with no annotations, no output schema, and zero schema description coverage, the definition is too thin. It omits query semantics, pagination behavior, source and sorting meaning, and result ordering, all of which an agent needs to invoke it accurately.

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

Parameters1/5

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

There are five parameters and schema description coverage is 0%. The description never mentions query, start, source, sort_by, or max_results, so it adds no meaning beyond the bare parameter names and defaults; the required compensation for missing schema documentation is absent.

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 states a clear verb and resource: 'Search academic papers.' It names get_paper as the follow-up tool but does not distinguish this search from siblings like search_papers_bulk, search_all, or search_snippets, leaving the agent to guess which search variant to use.

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?

It gives one useful routing hint: call get_paper for the full record after previewing results. It provides no when-to-use guidance versus the many other search tools, no exclusions, and no prerequisites, so usage is only implied.

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.