Skip to main content
Glama

autocomplete_papers

Semantic Scholar: autocomplete paper titles for a partial query (fast type-ahead).

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It identifies the tool as a fast type-ahead autocomplete, which is useful context, but it does not describe result limits, matching semantics, or any rate or auth considerations.

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?

The description is a single front-loaded sentence with no redundant wording. It compactly communicates the source, action, input condition, and interaction style.

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?

For a simple one-parameter autocomplete tool with no output schema, the description covers the core purpose but omits what the response contains and any behavioral caveats. It is adequate but leaves some useful context unstated.

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 input schema has one parameter at 0% description coverage, and the description only clarifies that 'query' should be a partial query. That adds some meaning beyond the bare schema but does not specify constraints such as maximum length or matching rules.

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 specific action ('autocomplete paper titles'), the input type ('partial query'), and adds 'fast type-ahead' as the mode. It is clear what the tool does, though it does not explicitly name how it differs from sibling tools such as search_papers or match_paper_title.

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 phrase 'fast type-ahead' implies this should be used for interactive, partial-query completion rather than full search. However, the description does not state when to use this instead of search_papers or match_paper_title, so usage guidance 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.