Skip to main content
Glama

Semanticscholar Get Author

semanticscholar_get_author
Read-onlyIdempotent

Search for academic authors by name on Semantic Scholar. Returns up to 5 matches with affiliations, paper count, total citation count, h-index, and profile URL. Keyless.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "Yoshua Bengio"
    },
    "name": "semanticscholar_get_author"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesAuthor name to search for, e.g. "Yoshua Bengio".

Output Schema

NameRequiredDescriptionDefault
countNo
authorsNo
licenseNo
attributionNo
license_noteNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare read-only, open-world, idempotent, non-destructive behavior, so the bar is lower. The description still adds real value beyond them: the hard cap of 5 results, the exact fields returned, and that the tool is keyless (no auth/API key needed). It does not cover rate limits or empty-result behavior, keeping it short of a 5.

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?

Three short sentences, front-loaded with the action, then the return shape, then the access constraint. Every sentence contributes information and nothing is repeated from the schema.

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

Completeness5/5

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

For a one-parameter lookup with an output schema present, the description covers everything an agent needs: what it searches, how many results come back, what fields those results contain, and that no key is required.

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

Parameters4/5

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

With a single parameter at 100% schema description coverage, the schema already carries the semantics, and the description's 'by name' framing plus the inline example reinforce it. No additional syntax or formatting guidance is offered, but none is really needed for a free-text name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Search for academic authors by name on Semantic Scholar'), which cleanly separates it from the paper-oriented siblings like semanticscholar_get_paper and semanticscholar_search_papers. An agent can pick this tool without opening the schema.

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 'Search for academic authors by name' implies the use case, but there is no explicit when-to-use/when-not guidance or named alternative (e.g., what to do if you already have an author ID). Usage is inferable rather than stated.

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.