DocImprint

Summarize Document

summarize_document

Read-onlyIdempotent

Summarize document text into a prose summary and key points with citations. Use after extract_text or extract_url when you need a condensed understanding of a long document. For single-sentence Q&A, use qa_url instead. For extracting specific fields, use extract_structured. Typical workflow: extract_text/extract_url → summarize_document. Returns: { summary: string, key_points: string[], summary_cited: { value, confidence, citations[] }, key_points_cited: [{ text, citations[] }], truncated: boolean, strategy: "full"|"truncated"|"chunked" } Example prompts:

"Summarize this financial report and give me the key points."
"What are the main takeaways from this document?"
"Give me a concise summary of this 50-page report."

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes	Document text to summarize. Obtain via extract_text or extract_url. Example: "The Q4 2025 financial report shows revenue growth of 23% year-over-year..."
`max_tokens`	No	Input length cap (1 token ≈ 4 chars). Default ~3000 tokens. Truncates input, not output. Example: 4000

Output Schema

TableJSON Schema

Name	Required	Description	Default
`summary`	Yes
`strategy`	Yes
`truncated`	Yes
`key_points`	Yes
`summary_cited`	Yes
`key_points_cited`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 29, 2026
RemovedJul 26, 2026

Changed1 schema field changedJul 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "key_points": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "key_points_cited": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "citations": {
+            "items": {
+              "additionalProperties": false,
+              "properties": {
+                "artifact": {
+                  "type": "string"
+                },
+                "char_end": {
+                  "type": "number"
+                },
+                "char_start": {
+                  "type": "number"
+                },
+                "chunk_id": {
+                  "type": "string"
+                },
+                "confidence": {
+                  "enum": [
+                    "high",
+                    "medium",
+                    "low"
+                  ],
+                  "type": "string"
+                },
+                "page": {
+                  "type": "number"
+                },
+                "paragraphs": {
+                  "items": {
+                    "type": "number"
+                  },
+                  "type": "array"
+                },
+                "quote": {
+                  "type": "string"
+                }
+              },
+              "required": [
+                "quote",
+                "paragraphs",
+                "confidence"
+              ],
+              "type": "object"
+            },
+            "type": "array"
+          },
+          "text": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "text",
+          "citations"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "strategy": {
+      "enum": [
+        "full",
+        "truncated",
+        "chunked"
+      ],
+      "type": "string"
+    },
+    "summary": {
+      "type": "string"
+    },
+    "summary_cited": {
+      "additionalProperties": false,
+      "properties": {
+        "citations": {
+          "items": {
+            "additionalProperties": false,
+            "properties": {
+              "artifact": {
+                "type": "string"
+              },
+              "char_end": {
+                "type": "number"
+              },
+              "char_start": {
+                "type": "number"
+              },
+              "chunk_id": {
+                "type": "string"
+              },
+              "confidence": {
+                "enum": [
+                  "high",
+                  "medium",
+                  "low"
+                ],
+                "type": "string"
+              },
+              "page": {
+                "type": "number"
+              },
+              "paragraphs": {
+                "items": {
+                  "type": "number"
+                },
+                "type": "array"
+              },
+              "quote": {
+                "type": "string"
+              }
+            },
+            "required": [
+              "quote",
+              "paragraphs",
+              "confidence"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "confidence": {
+          "enum": [
+            "high",
+            "medium",
+            "low"
+          ],
+          "type": "string"
+        },
+        "value": {}
+      },
+      "required": [
+        "value",
+        "confidence",
+        "citations"
+      ],
+      "type": "object"
+    },
+    "truncated": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "summary",
+    "key_points",
+    "summary_cited",
+    "key_points_cited",
+    "truncated",
+    "strategy"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedJun 24, 2026

changedInput schema / properties / max_tokens / description

Previous value: -"Input length cap (1 token ≈ 4 chars). Default ~3000 tokens. Truncates input, not output."New value: +"Input length cap (1 token ≈ 4 chars). Default ~3000 tokens. Truncates input, not output. Example: 4000"

changedInput schema / properties / text / description

Previous value: -"Document text to summarize. Obtain via extract_text or extract_url."New value: +"Document text to summarize. Obtain via extract_text or extract_url. Example: \"The Q4 2025 financial report shows revenue growth of 23% year-over-year...\""

First observedJun 10, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint and idempotentHint, covering safety and repeatability. The description adds valuable behavioral detail beyond annotations: the exact return structure, the 'truncated' flag, and the 'strategy' values (full/truncated/chunked). It does not cover error handling or rate limits, but for a read-only summarizer this is a minor gap.

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?

The description is front-loaded with purpose, then usage, workflow, return structure, and example prompts. It is well-organized and every section earns its place, though the example prompts are somewhat redundant for an agent that already understands the tool's purpose and alternatives.

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 the tool's complexity (summarization with citations), the rich input schema, clear annotations, and presence of an output schema, the description is complete. It covers purpose, workflow, alternatives, and even return value details, leaving no obvious gaps for an agent to invoke it correctly.

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 detailed descriptions for 'text' and 'max_tokens' including examples and the note that max_tokens truncates input, not output. The description itself adds no parameter-level semantics beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

States a specific verb (Summarize) and resource (document text) and explicitly distinguishes from siblings by naming alternatives: qa_url for single-sentence Q&A and extract_structured for extracting specific fields. An agent can select this tool without opening other definitions.

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

Usage Guidelines5/5

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

Provides explicit when-to-use context: 'Use after extract_text or extract_url when you need a condensed understanding of a long document.' It also names alternatives and the condition that selects them, plus a typical workflow 'extract_text/extract_url → summarize_document'.

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

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