Skip to main content
Glama

PaperList

Search

search
Read-onlyIdempotent

Search Paperlist papers by keywords. Returns ids to pass to fetch.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Output Schema

NameRequiredDescriptionDefault
noteNo
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar is lower. The description adds the useful chaining detail that results are IDs intended for fetch, but says nothing about matching semantics (substring vs full-text, ranking, case sensitivity) or result limits/pagination, which materially affect how an agent queries and consumes output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the core purpose is front-loaded ahead of the output-chaining note. Slightly terse and relies on unexplained product jargon ('Paperlist'), which weakens the structure marginally but there is no wasted wording.

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

Completeness3/5

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

An output schema exists, so the description need not explain return values, and annotations cover the safety profile. Still missing for a one-parameter search tool is any statement of match behavior and any differentiation from the sibling search_papers, leaving the agent to guess at both query formulation and tool selection.

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?

The single 'query' parameter has 0% schema description coverage beyond a maxLength constraint, so the description must carry the burden. Saying 'by keywords' does establish that the input is free-text terms rather than an ID or structured filter, but it does not clarify tokenization, multi-word behavior, boolean syntax, or whether operators are supported.

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: 'Search Paperlist papers by keywords', which is clearly a keyword-based paper lookup rather than a retrieval-by-id or topic-stats operation. It does not differentiate itself from close siblings such as search_papers or find_similar_papers, so an agent cannot tell which of the similarly named search tools to pick from the description alone.

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?

The clause 'Returns ids to pass to fetch' gives an implied two-step workflow, telling the agent this is an entry point rather than a terminal lookup. However, there is no explicit when-not guidance, no explanation of how it differs from the sibling search_papers tool, and no note on when find_similar_papers would be preferred.

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