tomesphere

get_paper

Read-only

Fetch a paper's full metadata: title, authors, year, abstract, TLDR (LLM-generated), key findings, citation count, GitHub repos, HuggingFace models/datasets, videos, peer reviews, and links. Accepts an arXiv ID (e.g. '2401.12345' or '1706.03762v5') or an OpenAlex Work ID (e.g. 'W4390723197'). Use when the user names a specific paper or pastes an arXiv link.

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": {
      "id": "<id>"
    },
    "name": "get_paper"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	arXiv ID like '2401.12345' or OpenAlex Work ID like 'W4390723197'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 6, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds return field details (TLDR, GitHub repos, etc.) without contradicting annotations. No additional behavioral disclosure needed beyond annotations.

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 sentences, first sentence lists return fields, second gives usage guidance. No wasted words, front-loaded with action.

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?

Single parameter with full schema coverage, no output schema needed. Description comprehensively explains return values and ID formats, sufficient for retrieval tool.

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?

Schema coverage is 100%, but description adds meaningful context for the 'id' parameter by specifying accepted formats (arXiv ID vs OpenAlex Work ID) and usage scenario beyond the schema description.

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?

The description clearly states the verb 'Fetch' and the resource 'paper's full metadata', listing specific fields. It distinguishes from siblings like search_papers by noting it is for a specific paper or arXiv link.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: 'when the user names a specific paper or pastes an arXiv link.' Provides accepted ID formats but does not mention when not to use or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All tomesphere tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?