sensefold

Fetch Sensefold document

fetch

Read-only

Retrieve the text of a saved Sensefold document by ID for reading and citation. Returns {id, title, text, url, metadata}. Most documents arrive complete in one call; long documents are served in sequential parts - when metadata.truncated is true, call fetch again with metadata.next_id to get the next part (a position banner at the top of text states the covered range). url is the document's address in the user's library; metadata.source_url is where the material was originally captured from, if anywhere. Get IDs from search or search_hub results.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes	Item UUID from search results, or a continuation id from metadata.next_id.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`id`	Yes
`url`	Yes
`text`	Yes
`title`	Yes
`metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedSep 15, 2026

addedOutput schema / properties / metadata / properties / content_base

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "images": {
+          "additionalProperties": false,
+          "properties": {
+            "dir": {
+              "type": "string"
+            },
+            "root": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "dir",
+            "root"
+          ],
+          "type": "object"
+        },
+        "links": {
+          "additionalProperties": false,
+          "properties": {
+            "dir": {
+              "type": "string"
+            },
+            "root": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "dir",
+            "root"
+          ],
+          "type": "object"
+        }
+      },
+      "required": [
+        "links",
+        "images"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / metadata / required

Previous value: -[
-  "truncated",
-  "start",
-  "end",
-  "total_chars",
-  "source_url"
-]New value: +[
+  "truncated",
+  "start",
+  "end",
+  "total_chars",
+  "source_url",
+  "content_base"
+]

First observedSep 13, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint, and the description adds substantial behavioral detail: the return shape, pagination behavior via truncated/next_id, position banner for long documents, and the distinction between url and metadata.source_url. This goes well beyond what the annotations alone 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?

The description is dense but every sentence earns its place. It front-loads the core purpose, then covers the return shape, pagination, URL semantics, and ID sourcing in a compact, logical order without padding.

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?

Given a single parameter, an output schema, and annotations that already signal read-only behavior, the description covers everything an agent needs: how to obtain an ID, what response to expect, and exactly how to page through truncated documents. There are no significant gaps.

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?

The input schema fully documents id as a UUID from search results or a continuation id from metadata.next_id, so the schema does the heavy lifting. The description repeats this information and adds that IDs come from search or search_hub, but it does not add meaningful new parameter meaning 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?

The description states a specific verb ('retrieve'), a specific resource ('text of a saved Sensefold document by ID'), and the intended use ('for reading and citation'). It is clear and accurate, but it does not explicitly contrast this tool with siblings like get_item or list_items, so the differentiation is implicit rather than stated.

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?

The description gives clear usage context: IDs come from search or search_hub, and fetch should be called again with metadata.next_id when truncated is true. It lacks explicit exclusions or when-not-to-use guidance relative to sibling tools, but the continuation protocol is well explained.

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

All sensefold 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.