Skip to main content
Glama

get_ransomware_stats_by_country

Get ransomware attack statistics by country from Vysion. Use to see which countries are most targeted by ransomware.

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": "get_ransomware_stats_by_country"
  }
}

Input Schema

NameRequiredDescriptionDefault
gteNoDate in YYYY-MM-DD format
lteNoDate in YYYY-MM-DD format
countriesNoCountry codes comma-separated (e.g., 'US,DE,ES')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/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 behavioral burden. It never says whether results are aggregated counts or raw attack rows, whether the date range has defaults, how large the result set can be, or whether the fields are optional and what happens when omitted. The only extra text is a boilerplate HTTP 200 note, which adds nothing about behavior.

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 substantive description is two short, front-loaded sentences with no waste. The appended 'Responses: 200 / Content-Type' block is transport boilerplate that does not help an agent decide or invoke, so it is minor noise.

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?

For a three-optional-parameter read tool with no output schema and no annotations, the definition covers the purpose but leaves the return shape and default date-range behavior unexplained. An agent knows what the tool is for but not what it will get back or how to interpret an empty country list.

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% and all three parameters (gte, lte, countries) are documented in the schema with formats and examples. The description adds no meaning beyond that, which is acceptable given the schema does the work.

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 ransomware attack statistics by country') plus the data source (Vysion), which is enough to separate it from siblings like get_ransomware_stats_by_group and get_ransomware_stats_by_sector. It does not explicitly name those alternatives, but the resource scope is unambiguous.

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?

The second sentence gives a clear use case — seeing which countries are most targeted — which tells the agent what question this tool answers. It lacks any exclusion or prerequisite guidance (e.g., when to use the by-group or by-sector variants instead), so it stops short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources