Vysion

search_ransomware_victims

Search Vysion's ransomware victim database by organization name, group, country, or industry. Returns records of ransomware attacks. Filter by organization name, ransomware group (LockBit, ALPHV, Qilin, etc.), country, industry, and date range. Use to investigate specific victims or track group activity over time.

Responses:

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

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

Name	Required	Description
`q`	No	Organization name or search term
`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
`group`	No	Ransomware group name (e.g., 'LockBit', 'ALPHV')
`country`	No	Victim country code (e.g., 'US', 'DE')
`industry`	No	Industry sector
`page_size`	No	Items per page

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

B3.4/5.0

Behavior3/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 establishes that this is a read/search operation returning attack records and that filtering is available, but says nothing about pagination behavior (despite page and page_size parameters), result ordering, total counts, or any auth/rate-limit constraints.

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 purpose is front-loaded in the first sentence and the whole thing is three sentences. There is mild redundancy: the first sentence's filter list is restated almost verbatim in the second sentence (organization name, group, country, industry).

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?

With 8 optional parameters, no output schema, and no annotations, the description should do more than it does. It never describes what a returned victim record contains or how paging results are shaped, leaving the agent to discover the response format empirically.

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 each of the 8 parameters is already documented, making 3 the baseline. The description corroborates the filter set and adds concrete example group values (LockBit, ALPHV, Qilin), but adds no syntax, matching rules, or defaults 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 gives a specific verb and resource ("Search Vysion's ransomware victim database") plus the dimensions it searches over, and states that it returns records of ransomware attacks. It is clearly distinguishable from sibling stats/histogram tools by implication, but never names an alternative such as get_ransomware_victim for single-record lookups.

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?

"Use to investigate specific victims or track group activity over time" supplies two positive use cases, so usage is more than implied. However, there are no exclusions and no routing to the many sibling tools (get_ransomware_victim, get_ransomware_stats_by_group, histogram endpoints) that overlap with "track group activity over time."

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?