Vysion

get_ransomware_misp_report

Get a specific ransomware MISP feed report by UUID. Use for MISP threat intelligence integration.

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": {
      "uuid_json": "<uuid_json>"
    },
    "name": "get_ransomware_misp_report"
  }
}

Input Schema

Name	Required	Description	Default
`uuid_json`	Yes	UUID of the MISP event (format: uuid.json)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden of behavioral disclosure. Beyond the tool name implying a read and the boilerplate '200: Successful Response' line, it says nothing about authentication, error behavior for unknown UUIDs, or what the report contains, which is a notable gap for an unannotated tool.

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 purpose sentence is front-loaded and short, but the appended '### Responses' block with content-type boilerplate is automatic-doc filler that does not help an agent decide or call the tool. Roughly half the text earns no place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a single-parameter retrieval with no annotations and no output schema, the description should at least sketch the report's contents or the failure mode for an invalid UUID. It leaves both unstated, so an agent knows the call signature but not what it will get back.

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 coverage is 100% and the schema already explains the UUID plus the '.json' format, so there is little left for the description to add. The phrase 'by UUID' aligns with the parameter but adds no new syntax or constraint information.

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 ('Get a specific ransomware MISP feed report') plus the lookup key ('by UUID'), so the agent knows this is a single-record retrieval tied to a UUID. It is implicitly separable from get_ransomware_misp_feed_manifest, but the description never names or contrasts with that sibling.

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

Usage Guidelines2/5

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

The only guidance is 'Use for MISP threat intelligence integration,' which restates the domain rather than giving a when-to-use condition. There is no indication of when to use this versus the feed manifest or the broader ransomware feed, and no prerequisites or exclusions.

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?