nodemaven-mcp

Official

Overview Schema Source Related Servers Discussions Admin

proxy_url

Read-only

Build a NodeMaven proxy URL with country, region, city, or ISP targeting. Add a session ID and TTL to keep the same exit IP for sticky requests.

Instructions

Build a NodeMaven proxy string.

Targeting goes into the username. Without session_id every request gets a
new exit IP; with session_id the same exit is kept for ttl (e.g. "10m",
"1h", "24h"). country is a two-letter code; region, city and isp take the
codes from list_locations. filter is the IP quality filter, e.g. "medium".
The password is a placeholder unless the server allows revealing it.

Input Schema

TableJSON Schema

Name	Required	Default
`isp`	No
`ttl`	No
`city`	No
`filter`	No
`region`	No
`country`	No
`protocol`	No	http
`session_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 6, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnly/destructive=false, so the description's added value is real: it explains sticky-vs-rotating exit IP behavior tied to session_id/ttl, and discloses that the password is a placeholder unless the server allows revealing it. That is meaningful behavioral context beyond the annotations.

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-loads the core purpose, then layers parameter semantics compactly with no filler. Slightly dense but every sentence earns its place.

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?

An output schema exists so return values need no explanation, and the description covers behavior and parameter meaning well. It omits that all 8 parameters are optional and the protocol parameter's meaning, which are minor gaps.

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 description coverage is 0%, so the description carries the full burden and largely meets it: it documents session_id, ttl (with example formats), country format, region/city/isp sourcing from list_locations, and filter. Only protocol is left unexplained, though its enum and default make it self-evident.

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+resource ('Build a NodeMaven proxy string'), which is distinguishable from siblings like check_proxy and list_locations. It does not explicitly name those siblings to route the agent, but the purpose 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 Guidelines3/5

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

It implies usage by pointing to list_locations for country/region/city/isp codes and explaining the session_id/ttl tradeoff, but it never says when to use this tool versus check_proxy or account_status, nor states prerequisites or when-not-to-use.

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

Deploy Server