Skip to main content
Glama

get_paper_references

Semantic Scholar: papers this one REFERENCES (its bibliography). id accepts S2 id / DOI: / ARXIV: / CorpusId:.

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

Input Schema

NameRequiredDescriptionDefault
startNo
paper_idYes
max_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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, and it mostly doesn't: nothing about whether results are paginated, how many are returned by default, ordering, or what the response contains. The one genuine disclosure is the accepted identifier prefixes (S2 id / DOI: / ARXIV: / CorpusId:), which is useful but narrow.

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?

Two tight sentences with zero filler, and the core operation is front-loaded before the identifier-format note. Nothing could be cut without losing information.

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

Completeness3/5

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

For a simple, read-only, three-parameter lookup without an output schema the bar is low, but with no annotations the description should still mention pagination behavior and roughly what comes back. As written it covers the identifier question well and leaves the paging semantics unexplained.

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

Parameters3/5

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

Schema coverage is 0%, so the description must compensate. It does well for paper_id by documenting four ID syntaxes, but says nothing about start or max_results beyond their self-evident names and defaults — no note that they drive pagination or their interaction.

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 — 'papers this one REFERENCES (its bibliography)' — with the directionality (outbound bibliography, not inbound citations) made explicit by the parenthetical. The 'Semantic Scholar:' prefix also disambiguates it from the sibling get_openalex_references, so an agent can pick correctly without opening either 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 intended use is strongly implied by the name and the 'REFERENCES' framing, but there is no explicit when-to-use statement, no mention of the reverse operation (get_paper_citations) as an alternative, and no prerequisites. An agent must infer that this is the outbound-citation counterpart.

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.