Skip to main content
Glama
NovadaLabs

novada-mcp

Official
by NovadaLabs
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

novada_proxy_mobile

Read-onlyIdempotent

Route requests through real 4G/5G mobile IPs to access mobile-targeted content and app APIs. Supports geo-targeting by country and carrier, plus sticky sessions.

Instructions

Route requests through 4G/5G mobile IPs — real mobile device IPs ideal for mobile-targeted content and apps.

Best for: Mobile-targeted content, app APIs, platforms serving different content to mobile vs desktop. Not for: novada_extract or novada_crawl — they handle proxy routing internally. These credentials are for your own HTTP clients (curl, requests, axios). Params: url (optional), country (ISO 2-letter, optional), carrier (optional, e.g. 'verizon'), session_id (optional for sticky IP). Formats: "url", "env", "curl". agent_instruction: Mobile IPs. Best for mobile-targeted content and apps. Pair with mobile User-Agent for full simulation. Requires: NOVADA_PROXY_USER, NOVADA_PROXY_PASS, NOVADA_PROXY_ENDPOINT env vars.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoOptional target URL. When provided, returns config scoped for that URL. Omit for generic proxy credentials.
countryNoISO 2-letter country code for geo-targeting (e.g. 'us', 'gb'). Use to access mobile-targeted content from a specific region.
carrierNoMobile carrier name for carrier-level targeting (e.g. 'verizon', 'att', 't-mobile'). Optional.
session_idNoSession ID for sticky mobile IP routing. Use for multi-step workflows requiring consistent mobile IP.
formatYesOutput format. 'url': proxy URL string (default). 'env': shell export commands. 'curl': curl --proxy flag.url

Tool Definition Quality

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and the description adds practical behavioral context such as requiring environment variables and being for external HTTP clients, but does not contradict 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?

Description is well-structured with bold headers and bullet points, front-loading the key purpose. It is somewhat lengthy but every sentence adds value, with no redundancy.

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?

The description covers purpose, usage context, parameter summary, required environment variables, and format options, and differentiates from sibling proxy tools, making it complete for a proxy configuration tool with no output schema.

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% with descriptions for all parameters. The description summarizes parameters and adds minor context (e.g., 'sticky IP' for session_id), but the schema already provides sufficient meaning, so baseline 3 is appropriate.

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 the tool routes requests through 4G/5G mobile IPs, specifying the resource (mobile IPs) and verb (route), and distinguishes it from siblings by focusing on mobile-targeted content.

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 lists best-for and not-for scenarios, including specific sibling tools (novada_extract, novada_crawl) and clarifies these credentials are for external HTTP clients, providing excellent guidance on when to use.

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/NovadaLabs/novada-mcp'

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