Skip to main content
Glama
3APA3A-3AHO3A

remnawave-mcp

by 3APA3A-3AHO3A
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

geocheck_node

Read-only

Checks a node's IP as seen by external services, returning country, blocks, reputation, and route targets; add full:true for traceroute hops.

Instructions

Run GeoCheck on a node and wait for the result (how services see the node IP: country, blocks). Returns a compact report: country per service and GeoIP base, reputation, blocks, one line per route target. Pass full: true for the raw report with every traceroute hop (large); the SVG image is always dropped. Uses node traffic: repeated calls for the same node within the cooldown return the previous result (also with full: true — it does not start a new check).

Input Schema

NameRequiredDescriptionDefault
ipNoOptional: check from this outbound IP
fullNoReturn the raw report with traceroute hops (large)
nodeUuidYesNode UUID (see get_nodes / panel_overview)
interfaceNoOptional: check from this network interface
timeoutSecNoMax seconds to wait for the node to answer

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.4.5
    • addedInput schema / properties / full
      Added value: +{
+  "default": false,
+  "description": "Return the raw report with traceroute hops (large)",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.3.0
    • changedInput schema / properties / nodeUuid / description
      Previous value: -"Node UUID (see get_nodes)"New value: +"Node UUID (see get_nodes / panel_overview)"
  3. First observedv1.1.1

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond readOnlyHint=true: discloses that the call consumes node traffic, that repeated calls within a cooldown return the cached prior result (even with full: true, which will surprise an agent expecting fresh data), and that the SVG image is always stripped from output. These are exactly the hidden behaviors an agent needs before calling.

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-loaded purpose, then output shape, then the full/cooldown caveat — a logical order with no filler. Slightly dense with stacked parentheticals, but each clause carries information an agent needs.

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

Completeness5/5

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

With no output schema, the description fully compensates by enumerating what the report contains (country per service, GeoIP base, reputation, blocks, one line per route target) and noting the dropped SVG. Combined with cache and timeout semantics, an agent has enough to call it correctly and interpret the result.

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 coverage is 100%, so baseline is 3; the description still adds real meaning by explaining the size tradeoff of full and, critically, that full: true does NOT bypass the cooldown cache. The ip/interface/timeoutSec params are left to the schema, which is acceptable given full coverage.

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?

Opens with a specific verb+resource ('Run GeoCheck on a node and wait for the result') and immediately clarifies the semantic ('how services see the node IP: country, blocks'), which separates it from inspection siblings like get_node, get_node_metadata, and node_connections.

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?

Gives clear conditional guidance for the main fork ('Pass full: true for the raw report... (large)') and warns about the cooldown reuse behavior. It doesn't explicitly name an alternative tool when a full GeoCheck is unnecessary (e.g. get_node_metadata for static info), so not quite a 5.

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