Skip to main content
Glama

1001SMS: Virtual Numbers & eSIMs

get_proxy_usage

Requests per day over the last month for one proxy plan.

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>"
    },
    "name": "get_proxy_usage"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeYesThe proxy type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add genuinely behavioral context — daily granularity and a one-month window — which goes beyond the schema, but it says nothing about return format, whether the history is bounded, auth requirements, or rate limits.

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?

One short sentence with zero padding, front-loaded with the metric and scoped by timeframe and segment. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple single-parameter read tool with no output schema, the description covers what is measured and over what window, which is close to sufficient. It is thin on scope edges (is the period rolling or calendar, per-plan aggregation vs totals) given there are no annotations to fill the gap.

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?

The single parameter is fully documented in the schema, including its enum values, so the baseline is 3. The description adds no meaning beyond that and its phrase 'one proxy plan' mildly conflicts with a parameter that selects a proxy type rather than a plan, which could momentarily misdirect an agent.

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?

The description names a specific metric (requests per day), a timeframe (last month) and a scope (one proxy plan), which clearly distinguishes this from siblings like get_proxy_plan or get_proxy_pricing. It stops short of an explicit verb such as 'retrieve' and uses 'proxy plan' where the tool actually segments by proxy type, leaving a small ambiguity.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when not to use it, and no pointer to any alternative among the many get_proxy_*/get_stats siblings. The agent must infer from the metric alone that this is the usage-reporting tool.

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