Skip to main content
Glama
Sign In

Prokso Proxy

by com.prokso
OverviewDiscussionsAdmin

Prices

get_prices
Read-only

Get current prices per GB for residential, mobile and datacenter proxies, including volume tiers and the minimum order when paying from the balance. Use it to estimate the cost of a task; it does not buy anything. Takes no arguments.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is pre-established. The description adds meaningful reinforcement by stating it does not buy anything and takes no arguments, confirming there are no side effects or required inputs. It omits rate limits or caching of prices, but that gap is minor given the annotation coverage.

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?

Three short sentences, front-loaded with what is returned and followed by usage and invocation notes. Every sentence earns its place with no redundant restatement of the title.

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, single-purpose, parameterless read tool, the description covers what is returned (per-GB prices by proxy type, volume tiers, minimum order) and how to use it. It does not state currency or the response shape, but with no output schema and low complexity this is a small residual gap.

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?

The tool has zero parameters, which sets the baseline at 4. The description's closing line, "Takes no arguments," explicitly confirms this, leaving nothing for an agent to guess about invocation.

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?

States a specific verb and resource (get current prices per GB) and enumerates the proxy categories covered (residential, mobile, datacenter) plus what is included (volume tiers, minimum order from balance). This is clearly distinct from the sibling tools get_plan, list_plans, get_account, and get_proxy_lines.

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?

"Use it to estimate the cost of a task" gives explicit when-to-use guidance, and "it does not buy anything" rules out a purchase use case. It does not name an explicit alternative for actually purchasing, but for a zero-argument pricing lookup the context is clear.

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

All Prokso Proxy toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources