Skip to main content
Glama

get_authors_batch

Semantic Scholar: fetch many authors at once 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": {
      "ids": "<ids>"
    },
    "name": "get_authors_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/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 behavioral burden, and it discloses almost nothing: ordering of results, handling of unknown or partial ids, and whether missing authors are omitted or errors are all unstated. Nothing is said about rate limits, authentication, or return shape. The only disclosed trait is that multiple authors can be fetched in one call.

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 short sentence with the verb and scope front-loaded; nothing is padding. The 'Semantic Scholar:' prefix is redundant given the tool set and is the only wasted token.

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?

The tool is low-complexity (one required param, no nested objects), but with no annotations and no output schema the description must cover return behavior and failure modes, and it covers neither. An agent cannot tell what comes back for an id that does not resolve, or how results map to the input order.

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?

The single parameter has 0% schema description coverage, so 'by id' is the only signal, and it does usefully clarify that these are author identifiers rather than paper ids. It still omits accepted id formats (Semantic Scholar author id vs. ORCID/DOI), behavior for duplicate ids, and any length limit on the array.

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 ('fetch ... authors') plus a scope qualifier ('many at once by id') that separates it from the single-author sibling. The 'Semantic Scholar' prefix is redundant but harmless. It does not explicitly name get_author or search_authors, so differentiation is inferred from 'batch' and 'by id' rather than stated.

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?

'many at once by id' implies the caller should have a list of identifiers already in hand, which indirectly selects it over search_authors. However, there is no explicit when-to-use, when-not-to-use, or named alternative (get_author for a single lookup). Guidance is implied only.

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.