Skip to main content
Glama

search_authors

Semantic Scholar: search for authors by name; returns profiles with h-index and paper/citation counts.

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

Input Schema

NameRequiredDescriptionDefault
queryYes
startNo
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/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, and it does disclose the return payload (author profiles plus h-index and citation/paper counts), which is genuinely useful. However, it says nothing about it being a read-only operation, rate limits, authentication, or how pagination behaves despite having start/max_results parameters.

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?

A single compact sentence with the provider and purpose front-loaded and no filler. It is efficient, though it could have spent a few extra words on paging to close the largest gap.

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 three-parameter, read-only search with no output schema, the description covers what the tool does and what comes back, which is the core need. It is incomplete on pagination behavior and on how it relates to the many sibling search/lookup tools, leaving the agent to infer both.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate for all three parameters. It only clarifies that 'query' is an author name; 'start' and 'max_results' get no explanation of paging semantics, defaults, or upper bounds beyond the schema's bare typing.

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 and resource ('search for authors by name') and names the provider ('Semantic Scholar'), which implicitly separates it from the OpenAlex-based siblings. It also states the shape of the result (profiles with h-index and paper/citation counts). It stops short of explicitly contrasting itself with tools like search_openalex_authors or get_author.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance: nothing says to prefer this over search_openalex_authors, or to use get_author when you already have an author ID, or get_authors_batch for multiple lookups. The name-search scope is only implied by the phrase 'by name'.

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.