There's An AI For That

Get paper details

get_paper

Read-only

Get public details for one published AI research paper by ID or slug. Preserve returned URLs exactly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	No	The exact numeric paper ID returned by search_papers.
`slug`	No	The paper slug returned by search_papers.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`paper`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 13, 2026

addedInput schema / oneOf

Added value: +[
+  {
+    "required": [
+      "id"
+    ]
+  },
+  {
+    "required": [
+      "slug"
+    ]
+  }
+]

addedInput schema / properties / id

Added value: +{
+  "description": "The exact numeric paper ID returned by search_papers.",
+  "minimum": 1,
+  "type": "integer"
+}

removedInput schema / required
```
Removed value: -[
-  "slug"
-]
```
addedOutput schema / properties / paper / properties / attributes / properties / authors / items / type
```
Added value: +"string"
```

addedOutput schema / properties / paper / properties / attributes / properties / companies

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / paper / properties / attributes / properties / organizations

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / paper / properties / attributes / properties / related_models

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / paper / properties / attributes / properties / related_repositories

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

addedOutput schema / properties / paper / properties / attributes / properties / related_tools

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "id": {
+        "type": "integer"
+      },
+      "name": {
+        "type": "string"
+      },
+      "slug": {
+        "type": "string"
+      },
+      "url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "slug",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": [
+    "array",
+    "null"
+  ]
+}

AddedSep 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly, non-destructive, and closed-world behavior, so the burden is light. The description still adds two pieces of non-structured context: only public/published papers are returned, and returned URLs must be preserved exactly (an output-handling caution) – useful beyond what annotations provide.

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 short sentences with zero filler; the core purpose is front-loaded and the URL-preservation caveat is placed second as an operational note. Nothing is wasted.

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

Completeness4/5

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

For a simple, single-entity read tool with complete schema coverage, safety annotations, and an output schema that documents the return shape, the description covers what is needed. The only thin area is when to prefer this over the search tools, but that is minor at this complexity.

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?

With 100% schema description coverage, the schema already explains both 'id' and 'slug' and the oneOf requirement, so the baseline is 3. The description repeats 'by ID or slug' without adding format, precedence, or fallback guidance beyond the schema.

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 ('Get public details for one published AI research paper') with scope qualifiers ('public', 'published', 'one'), which distinguishes it from the search_papers sibling in the adjacent set. It does not explicitly name the sibling tool in the description, so it falls short of a 5.

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: the parameter descriptions note the ID and slug come 'returned by search_papers', which suggests the search-then-fetch workflow. There is no explicit when-to-use/when-not statement or naming of alternatives, so this is minimum-viable rather than strong guidance.

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

All There's An AI For That 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.