Skip to main content
Glama

get_paper_authors

Semantic Scholar: the authors of a paper (with h-index, 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": {
      "paper_id": "<paper_id>"
    },
    "name": "get_paper_authors"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
paper_idYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses only that author records include h-index and paper/citation counts; it says nothing about pagination behavior, ordering, result limits, or whether a missing paper returns an error versus an empty list.

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?

One tight phrase with no wasted words, and the key noun ('authors of a paper') is front-loaded after the source prefix. The brevity is efficient rather than padded, though it tips into under-specification elsewhere.

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?

With no annotations, no output schema, no parameter descriptions, and three parameters including a pagination pair, the description does too little to let an agent call this correctly. The identifier-format and pagination details an agent needs are entirely absent.

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?

Schema description coverage is 0% across three parameters (paper_id, start, max_results) and the description adds no clarifying meaning. Critically, it does not explain that paper_id accepts multiple identifier formats (DOI, arXiv ID, corpus ID), which is the single most error-prone part of calling this tool.

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 names a specific resource ('the authors of a paper') and its source ('Semantic Scholar'), and even hints at the payload (h-index, paper/citation counts). It is clear what the tool returns, but it does not distinguish itself from nearby tools such as get_author_papers or get_authors_batch.

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 guidance on when to use this versus alternatives like get_author (single author lookup) or get_authors_batch, nor on prerequisites such as needing a valid paper identifier. The agent must infer the use case from the name alone.

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.