Skip to main content
Glama

get_author_papers

Semantic Scholar: all papers by a given author id, newest first.

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": {
      "author_id": "<author_id>"
    },
    "name": "get_author_papers"
  }
}

Input Schema

NameRequiredDescriptionDefault
startNo
author_idYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/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 burden. It discloses the data source (Semantic Scholar) and result ordering, but says nothing about pagination limits, behavior for an unknown author ID, rate limits, or what fields each paper carries.

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 source and sort order front-loaded and no filler. It is efficient, though the terseness contributes to the missing pagination and return-shape context.

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 tool with no annotations, no output schema, and 0% parameter documentation, the description does too little. An agent still lacks pagination behavior, return shape, and error handling for an unknown author ID.

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% across three parameters, and the description only clarifies author_id plus the implicit ordering. The pagination parameters 'start' and 'max_results' are never explained, so the agent must guess at their semantics and any upper bound.

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 ('all papers by a given author id') plus the sort order ('newest first'), which is enough to tell it apart from get_paper_authors or search_by_author. It stops short of explicitly naming a sibling to disambiguate against, so it lands at 4 rather than 5.

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 and no alternatives named. The phrase 'by a given author id' faintly implies the prerequisite of already having an author ID, but nothing tells the agent when to prefer this over search_by_author or get_author.

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.