Paperswithcode

Get Paper

get_paper

Read-onlyIdempotent

Get full detail for a paper by its arXiv id (e.g. "2312.00752"): title, authors, abstract, AI-generated summary and keywords, community upvotes, and counts of linked models / datasets / demo Spaces.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`arxiv_id`	Yes	arXiv identifier (e.g. "2312.00752").

Output Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Papers With Code paper ID
`title`	Yes	Paper title
`authors`	Yes	List of paper authors
`url_abs`	Yes	URL to paper abstract
`url_pdf`	Yes	URL to paper PDF
`abstract`	Yes	Paper abstract
`arxiv_id`	Yes	ArXiv ID of the paper
`published`	Yes	Publication date
`conference`	Yes	Conference name
`proceeding`	Yes	Proceeding identifier

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedJul 29, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "id": "attention-is-all-you-need"
-  }
-]New value: +[
+  {
+    "arxiv_id": "2312.00752"
+  }
+]

Changed3 schema fields changedJun 25, 2026

addedInput schema / properties / arxiv_id

Added value: +{
+  "description": "arXiv identifier (e.g. \"2312.00752\").",
+  "type": "string"
+}

removedInput schema / properties / id

Removed value: -{
-  "description": "Papers With Code paper ID (e.g., \"attention-is-all-you-need\")",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "id"
-]New value: +[
+  "arxiv_id"
+]

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "id": "attention-is-all-you-need"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "abstract": {
+      "description": "Paper abstract",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "arxiv_id": {
+      "description": "ArXiv ID of the paper",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "authors": {
+      "description": "List of paper authors",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "conference": {
+      "description": "Conference name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "Papers With Code paper ID",
+      "type": "string"
+    },
+    "proceeding": {
+      "description": "Proceeding identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "published": {
+      "description": "Publication date",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "title": {
+      "description": "Paper title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url_abs": {
+      "description": "URL to paper abstract",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "url_pdf": {
+      "description": "URL to paper PDF",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "arxiv_id",
+    "title",
+    "abstract",
+    "authors",
+    "published",
+    "conference",
+    "proceeding",
+    "url_abs",
+    "url_pdf"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 11, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "_apiKey": "your-core-research-api-key",
-    "id": "123456789"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "abstract": {
-      "description": "Paper abstract",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "authors": {
-      "description": "List of author names",
-      "items": {
-        "type": "string"
-      },
-      "type": "array"
-    },
-    "citation_count": {
-      "description": "Number of citations",
-      "type": [
-        "number",
-        "null"
-      ]
-    },
-    "doi": {
-      "description": "Digital Object Identifier",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "download_url": {
-      "description": "URL to download full paper",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "id": {
-      "description": "CORE paper ID",
-      "type": "string"
-    },
-    "language": {
-      "description": "ISO 639 language code",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "publisher": {
-      "description": "Publisher name",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "references_count": {
-      "description": "Number of references in the paper",
-      "type": "number"
-    },
-    "title": {
-      "description": "Paper title",
-      "type": [
-        "string",
-        "null"
-      ]
-    },
-    "year": {
-      "description": "Year of publication",
-      "type": [
-        "number",
-        "null"
-      ]
-    }
-  },
-  "required": [
-    "id",
-    "authors",
-    "references_count"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "abstract": {
+      "description": "Paper abstract",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "authors": {
+      "description": "List of author names",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "citation_count": {
+      "description": "Number of citations",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "doi": {
+      "description": "Digital Object Identifier",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "download_url": {
+      "description": "URL to download full paper",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "CORE paper ID",
+      "type": "string"
+    },
+    "language": {
+      "description": "ISO 639 language code",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "publisher": {
+      "description": "Publisher name",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "references_count": {
+      "description": "Number of references in the paper",
+      "type": "number"
+    },
+    "title": {
+      "description": "Paper title",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "year": {
+      "description": "Year of publication",
+      "type": [
+        "number",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "id",
+    "authors",
+    "references_count"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-core-research-api-key",
+    "id": "123456789"
+  }
+]

First observedApr 22, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Description lists specific return fields (title, authors, abstract, AI summary, etc.), adding value beyond annotations which only indicate read-only, open-world, idempotent, and non-destructive. No contradictions.

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?

Single sentence with no wasted words. Front-loaded with verb and resource.

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?

With output schema present, the description provides a complete overview of what the tool returns. No gaps for a simple read tool with one parameter.

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?

Single parameter 'arxiv_id' is described in both schema and description with example format. Schema coverage is 100%, so description adds minimal new meaning beyond the schema.

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?

Description clearly specifies verb 'Get', resource 'paper', and identifier 'arXiv id'. It lists what details are included, distinguishing it from sibling tools like search_papers (which searches) and trending_papers (trending list).

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?

Description implies use when you have an arXiv ID and want full details, but does not explicitly state when to use this tool vs alternatives (e.g., search_papers) or provide exclusions.

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

All Paperswithcode tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0

Disambiguation2/5

ask_pipeworx and ask_pipeworx_beta are currently identical in behavior, creating direct overlap. Additionally, the five query/research tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, bet_research) and six Polymarket tools have heavily overlapping boundaries that require reading long descriptions to disambiguate.

Naming Consistency3/5

Names are uniformly snake_case and mostly readable, with consistent domain prefixes (polymarket_*, pipeworx_*) and a verb_noun majority (get_paper, search_papers, resolve_entity). However, bare-verb memory tools (remember, recall, forget) and adjective-noun names (recent_alerts, trending_papers, deep_research) break the dominant convention, making the set mixed though not chaotic.

Tool Count2/5

At 35 tools, this exceeds the 25+ threshold for 'too many,' and several are near-duplicates or overlapping query modes (ask_pipeworx vs ask_pipeworx_beta vs ask_pipeworx_grounded). The server bundles paper search, a universal data router, prediction-market analytics, memory, subscriptions, dependency scanning, and AI visibility into one surface, which feels over-scoped.

Completeness4/5

The surface is quite thorough for its broad domain: querying has grounded/deep/meta variants, companies have profile/compare/change/claim tools, prediction markets have research/edges/arbitrage/fill-risk/spread tracking, and subscriptions/memory have full lifecycles. Minor gaps exist (no full pack catalog listing, no direct fetch-by-URI tool, no paper leaderboards), but agents can work around them via discover_tools/ask_pipeworx.

Get Paper

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

TDQS

Resources