Skip to main content
Glama
voidly-ai

@voidly/mcp-server

by voidly-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

get_high_risk_countries

Identify countries at elevated risk of internet shutdowns or censorship spikes within the next 7 days. Set a risk threshold to forecast where access disruptions are likely this week.

Instructions

Get countries with elevated censorship risk in the next 7 days. Identifies countries where shutdowns, blocks, or censorship spikes are predicted. Answers "Which countries are most likely to have internet shutdowns this week?"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
thresholdNoMinimum risk threshold (0.0-1.0, default 0.2 = 20% risk)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.0.2

TDQS

A3.8/5.0
Behavior3/5

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

No annotations provided. The description indicates it's a read-only prediction tool, but lacks details on data freshness, limitations, or any side effects.

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

Conciseness5/5

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

Two concise sentences with no fluff. Efficiently covers purpose and example usage.

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 simple tool with one optional parameter and no output schema, the description is sufficient. Could optionally mention the time horizon more explicitly.

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%. The description does not add extra meaning beyond what the schema already provides for the threshold parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets countries with elevated censorship risk in the next 7 days, and answers a specific question. The name is also informative.

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?

The description provides an implied use case but does not explicitly distinguish from siblings like get_censorship_index or get_risk_forecast. No when-not-to-use guidance.

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

Deploy Server

Other Tools