DocImprint

Ask a Question About a URL

qa_url

Read-only

Fetch a public HTTPS URL and answer a specific question about its content. Lean mode — no bundle stored. Use when you have a precise question about a web page. For a broad summary, use summarize_url. For multi-document Q&A, use ask_collection instead. Returns: { url, answer, answer_cited: { value, confidence, citations[] }, confidence: "high"|"medium"|"low", truncated } Example prompts:

"What is the refund policy at https://docs.example.com/policy?"
"Look at [URL] and tell me what the delivery terms are."
"Answer this question based on the content of [URL]: [question]."

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	Public HTTPS URL to fetch and question. Example: "https://docs.example.com/policy"
`question`	Yes	Specific question to answer from the page content. Example: "What is the refund policy?"
`max_tokens`	No	Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the answer. Example: 4000

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes
`answer`	No
`truncated`	Yes
`confidence`	No
`answer_cited`	No

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": {
+    "answer": {
+      "type": "string"
+    },
+    "answer_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"
+    },
+    "confidence": {
+      "enum": [
+        "high",
+        "medium",
+        "low"
+      ],
+      "type": "string"
+    },
+    "truncated": {
+      "type": "boolean"
+    },
+    "url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "url",
+    "truncated"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedJun 24, 2026

changedInput schema / properties / max_tokens / description

Previous value: -"Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the answer."New value: +"Input length cap (1 token ≈ 4 chars). Truncates fetched page content, not the answer. Example: 4000"

changedInput schema / properties / question / description

Previous value: -"Specific question to answer from the page content"New value: +"Specific question to answer from the page content. Example: \"What is the refund policy?\""

changedInput schema / properties / url / description

Previous value: -"Public HTTPS URL to fetch and question"New value: +"Public HTTPS URL to fetch and question. Example: \"https://docs.example.com/policy\""

First observedJun 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint, openWorldHint), but the description adds meaningful context beyond them: 'Lean mode — no bundle stored' discloses persistence behavior, and max_tokens is noted to truncate fetched content rather than the answer. It stops short of describing rate limits or error behavior, so a 4.

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?

Purpose, guidance, and returns are front-loaded in the first sentences with zero filler. The three example prompts are somewhat redundant given the clear prose, marginally costing conciseness but still illustrating realistic phrasing.

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?

With an output schema present, the description needn't detail return values, and safety is covered by annotations. The description still covers scope, alternatives, and the no-bundle/truncation behavior, leaving only edge cases like error or non-public URL handling unaddressed.

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%, so all three parameters are already documented, including the max_tokens truncation caveat. The description adds only example prompts and the HTTPS requirement, which the schema's uri format already implies. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ('Fetch a public HTTPS URL and answer a specific question about its content') and immediately disambiguates itself from summarize_url and ask_collection. An agent can distinguish this from all sibling extraction/QA tools without opening a schema.

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?

Explicit when-to-use ('a precise question about a web page') plus named alternatives for adjacent cases: summarize_url for broad summaries and ask_collection for multi-document Q&A. Routing conditions are fully spelled out, not left to inference.

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?