Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

quote_proxies

Price a proxy traffic order without buying: the volume discount and the exact total.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "gb": "<gb>"
    },
    "name": "quote_proxies"
  }
}

Input Schema

NameRequiredDescriptionDefault
gbYesWhole gigabytes
typeYesThe proxy type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does well: "without buying" declares the operation is non-mutating and safe to call speculatively. It also discloses the shape of the result (volume discount plus exact total), compensating for the absent output schema; auth requirements and rate limits are not addressed.

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?

A single sentence with the non-mutation guarantee front-loaded before the return detail; every clause earns its place and nothing is padded.

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 two-required-parameter read tool with full schema coverage, the definition covers purpose, safety profile, and output shape. The one meaningful gap is currency/units of the returned total, which an agent quoting a price would want to know.

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 description coverage is 100%, so both parameters (gb, type) are already documented with an enum. The description only adds that pricing is volume-based, which hints at why gb matters but gives no tier boundaries or currency context.

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 ("Price") and resource ("proxy traffic order") and immediately scopes it as non-purchasing ("without buying"), which cleanly separates it from order_proxies without requiring the schema to be opened.

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?

The phrase "without buying" establishes the use case as a pre-purchase price check, implicitly routing the agent to order_proxies when an actual purchase is intended. It stops short of naming the alternative explicitly or stating any preconditions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources