Vysion

search_documents

Search the Vysion darknet intelligence database for documents across Tor, I2P and clearnet. Covers darknet pages, forums, and marketplaces. Supports filters: date range, network type, language, and tags. Date window: when no start date (gte) is given, only the six months before lte (or before now) are searched. In that case, tell the user in your answer that the results only cover that six-month period, and ask whether they want the full history or a specific date range. When they ask for the full history or a period longer than six months, split it into sequential ranges of no more than six months (gte/lte) and run one search per range.

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": {
      "q": "<q>"
    },
    "name": "search_documents"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search query string
`gte`	No	Date in YYYY-MM-DD, ISO 8601, or Unix timestamp format
`lte`	No	Date in YYYY-MM-DD, ISO 8601, or Unix timestamp format
`page`	No	Page number
`network`	No	Network filter: Tor, I2P or Clearnet
`language`	No	Language filter (e.g., 'en', 'ru')
`page_size`	No	Items per page (max 100)
`exclude_tag`	No	Exclude documents with this tag
`include_tag`	No	Include documents with this tag

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the important default date-window constraint and the required agent behavior (notify user, ask, split ranges). It does not describe result format, pagination behavior, rate limits, or authentication needs, but the core behavioral constraint is well covered.

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?

Front-loads purpose and coverage, then filters, then date handling. The date section is somewhat long but every sentence serves a behavioral purpose. It could be tightened slightly, but it is well-structured and avoids unnecessary repetition.

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?

For a 9-parameter search tool with no annotations and no output schema, the description covers the key behavioral constraints: scope, filters, date-window default, and range splitting. It does not describe what results contain, pagination limits beyond schema defaults, or permission requirements, leaving minor gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline is 3. The description adds meaning beyond the schema: it explains that filters include date range, network, language, and tags, and crucially it defines the default date-window semantics for gte/lte (six months when gte is omitted) and the need to split longer ranges. This adds value not present in the schema descriptions.

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: 'Search the Vysion darknet intelligence database for documents across Tor, I2P and clearnet.' The scope is clear and it covers darknet pages, forums, and marketplaces. It does not explicitly name sibling tools like get_documents_by_email or get_document_by_id, so sibling differentiation is implied 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?

Provides explicit guidance for date handling: when no start date is given, only six months are searched; the agent must tell the user and ask about full history; longer periods must be split into sequential ranges of no more than six months. It lacks guidance on when to use this general search versus the many field-specific retrieval tools, so alternatives are not addressed.

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?