DeepMark

List Exam Papers

paper_list

Read-onlyIdempotent

List all exam papers with optional filtering

Input Schema

Name	Required	Description
`limit`	No	Maximum number of papers to return (pagination page size).
`offset`	No	Number of papers to skip before returning results (pagination).
`subject`	No	Filter to a single subject.

Output Schema

Name	Required	Description
`limit`	Yes
`offset`	Yes
`papers`	Yes
`has_more`	Yes	True when a full page came back — request the next offset.
`returned`	Yes	How many papers this page returned.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026

removedOutput schema / additionalProperties
```
Removed value: -false
```
removedOutput schema / properties / papers / items / additionalProperties
```
Removed value: -false
```

changedOutput schema / properties / papers / items / properties / created_by / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "email": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      },
-      "id": {
-        "type": "string"
-      },
-      "name": {
-        "anyOf": [
-          {
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ]
-      }
-    },
-    "required": [
-      "id",
-      "name",
-      "email"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "properties": {
+      "email": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "email"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

Changed2 schema fields changedOct 22, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

Changed5 schema fields changedAug 23, 2026

removedOutput schema / properties / papers / items / properties / created_by / additionalProperties
```
Removed value: -false
```

addedOutput schema / properties / papers / items / properties / created_by / anyOf

Added value: +[
+  {
+    "additionalProperties": false,
+    "properties": {
+      "email": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "id": {
+        "type": "string"
+      },
+      "name": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      }
+    },
+    "required": [
+      "id",
+      "name",
+      "email"
+    ],
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

removedOutput schema / properties / papers / items / properties / created_by / properties

Removed value: -{
-  "email": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  },
-  "id": {
-    "type": "string"
-  },
-  "name": {
-    "anyOf": [
-      {
-        "type": "string"
-      },
-      {
-        "type": "null"
-      }
-    ]
-  }
-}

removedOutput schema / properties / papers / items / properties / created_by / required
```
Removed value: -[
-  "id",
-  "name",
-  "email"
-]
```
removedOutput schema / properties / papers / items / properties / created_by / type
```
Removed value: -"object"
```

First observedJul 22, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so safety is covered. The description adds nothing beyond that — no mention of default page size behavior, ordering, or what an empty result means.

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?

A single front-loaded sentence with no filler. It is efficiently sized, though the brevity borders on under-specification rather than optimal conciseness.

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?

The tool is a simple read with an output schema and fully documented parameters, so structured data carries most of the burden. The description is technically sufficient to invoke but omits any note on ordering, default behavior or result shape nuances.

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 description coverage is 100% with pagination defaults and a full subject enum documented in the schema. The description's 'optional filtering' merely restates this, adding no syntax or format detail, so the baseline 3 applies.

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 ('List all exam papers'), clearly distinguishing the read/list operation from paper_get and paper_create. It does not explicitly name or contrast with siblings, which is required for 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 Guidelines2/5

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

Only 'with optional filtering' hints at usage; there is no guidance on when to use this vs paper_get, whether results are paginated by default, or any prerequisites. An agent must infer the selection context entirely.

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

All DeepMark 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?