Vysion

get_document_html_by_id

Retrieve the content of a darknet document from Vysion by its ID. By default returns the readable text of the page (format='text'); use format='html' only if you need the raw HTML markup.

Responses:

200: Successful Response (Success Response) Content-Type: application/json

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_document_html_by_id"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Document ID
`format`	No	'text' (readable page text, recommended) or 'html' (raw HTML)	text
`download`	No	Download the raw HTML as a file

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.3/5.0

Behavior3/5

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

No annotations exist, so the description carries the full load. It usefully discloses the default return shape (readable page text) versus raw markup, which is the key behavioral trait here, but says nothing about access requirements for darknet-sourced content, rate limits, or what the 'download' flag actually produces.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The two prose sentences are tight and front-loaded, but the appended '### Responses: 200 ... Content-Type: application/json' block is auto-generated boilerplate that restates nothing actionable and dilutes an otherwise efficient definition.

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?

A simple three-parameter read tool with full schema coverage and no output schema, so the bar is modest and the description clears the essentials. The unmentioned 'download' behavior and the missing distinction from get_document_by_id are the notable remaining 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?

Schema description coverage is 100%, so all three parameters are already documented, including the 'recommended' note on format. The description reinforces the format trade-off but adds no meaning beyond the schema and never mentions the third parameter, download.

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 ('Retrieve the content of a darknet document from Vysion by its ID') and clarifies the text-vs-HTML distinction the name hints at. It does not, however, differentiate itself from the sibling get_document_by_id, leaving an agent unsure which of the two similarly named tools to pick.

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?

Gives a clear rule for choosing between the format values ('use format='html' only if you need the raw HTML markup'), which is genuine conditional guidance. It offers no guidance on when to use this tool rather than get_document_by_id or search_documents, so sibling selection is 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 Vysion 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?