Skip to main content
Glama

get_author

Semantic Scholar: a single author's profile by id.

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

Input Schema

NameRequiredDescriptionDefault
author_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing beyond the data source. It does not say what happens when the id is unknown, whether an error or empty result is returned, whether calls are rate-limited or require a key, or what fields the profile contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The single fragment is front-loaded and free of waste, but it is terse to the point of under-specification – the brevity comes at the cost of the missing guidance noted above rather than from efficient editing.

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 simple one-parameter lookup the description is nearly adequate, but with no annotations, no output schema, and zero schema parameter coverage, the description is the only source of information and it omits identifier format, error behavior, and return contents.

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% for the single required parameter, so the description must compensate. 'By id' implies author_id is an identifier but never specifies the id namespace or format (Semantic Scholar author id vs ORCID vs external id), which is the key ambiguity given sibling lookup tools exist.

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 resource and scope: a single author's profile, keyed by id, from Semantic Scholar. The word 'profile' distinguishes it from get_author_papers and search_by_author, which target an author's works or a lookup by name rather than the profile itself.

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?

Usage is only implied by 'by id' – an agent can infer this is the fetch-by-identifier path versus search_by_author. There is no explicit when-to-use, no mention of what to do when only a name is known, and no note on whether the id must be a Semantic Scholar author id.

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.