Skip to main content
Glama
Artirain

nodemaven-mcp

by Artirain

nodemaven_check_proxy

Read-only

Send a test request through the proxy to verify exit IP, country, and latency before scraping, ensuring targeting resolves to the expected pool.

Instructions

Send one request through the proxy and report the exit IP, its geo and latency.

Use this before a scraping run to confirm the targeting resolves to a real pool and that the exit IP is where you expect. Over-narrow targeting (a rare city plus an ISP filter) is the usual reason a connection fails.

Returns: str: Markdown or JSON with the schema: { "exit_ip": str, # e.g. "104.28.51.7" "country": str, # e.g. "US" "region": str, "city": str, "org": str, "latency_ms": int, "proxy": str, # password-masked proxy URL "session_id_used": bool } On failure: "Error: "

Examples: - "am I really coming out of Germany?" -> country='de' - "does this sticky session hold?" -> session_id='ab12cd', call twice - Don't use when: you need the catalogue of available cities (use nodemaven_list_locations)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ispNoISP or mobile carrier to pin, e.g. 't-mobile usa'.
cityNoCity to narrow the pool, e.g. 'los angeles'.
portNoOverride the proxy port. Defaults to the port set for the protocol.
regionNoState or region to narrow the pool, e.g. 'california'.
countryYesTwo-letter ISO country code for the exit IP, e.g. 'us', 'de', 'br'.
protocolNoProxy protocol: 'http' or 'socks5'.http
ipv4_onlyNoRestrict the exit IP to IPv4.
session_idNo4-10 alphanumeric characters. Reuse the same value to keep the same exit IP across calls (sticky session); omit it to rotate on every request.
response_formatNo'markdown' for a compact summary, 'json' for the full payload.markdown
ip_quality_filterNoNodeMaven IP quality tier, e.g. 'medium' or 'high'.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description discloses that exactly one request is sent, describes the return schema and failure format, and notes that over-narrow targeting is a common failure cause. Annotations already mark it read-only, so the description adds beyond by explaining operational behavior. No contradiction.

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?

The description is well-structured with a clear opening, usage context, return schema, examples, and an exclusion. Each section earns its place, and it is not excessively verbose for a tool with 10 parameters.

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?

Given the tool's complexity (10 parameters), the description covers purpose, use cases, failure behavior, return format, and a sibling alternative. The schema and annotations supply parameter and safety details, so the description is contextually complete for an agent to select and invoke correctly.

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?

Although schema descriptions cover all parameters (100%), the description adds meaning with concrete examples: using country='de' to test exit country, and session_id='ab12cd' to test sticky sessions. It also explains the interplay of city and ISP for targeting. This goes beyond the schema.

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 uses a specific verb ('Send one request through the proxy') and clearly states the output (exit IP, geo, latency). It also distinguishes from sibling nodemaven_list_locations by explicitly stating when not to use it. This fulfills purpose clarity.

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

Usage Guidelines5/5

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

Explicitly states 'Use this before a scraping run to confirm...' and provides a 'Don't use when' with an alternative tool. This gives clear when-to-use and 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Artirain/nodemaven-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server