DoubleData MCP

Get bandwidth usage

get_usage

Read-only

Retrieve bandwidth, request counts, and wallet charges for a UTC date range, optionally filtered by credential username.

Instructions

Bandwidth bytes, request counts and wallet charges for a UTC date range, in total and per credential. Defaults to the current month. Use username to focus on one credential.

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_usage"
  }
}

Input Schema

Name	Required	Description
`to`	No	Exclusive UTC end date (YYYY-MM-DD). Must be 1 to 366 days after from.
`from`	No	Inclusive UTC start date (YYYY-MM-DD). Defaults to the current UTC month.
`username`	No	Limit the report to one proxy credential username.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real context beyond that: timezone semantics, default window, and dual aggregation (total plus per credential). It still says nothing about pagination, response size, or rate limits for a potentially large report.

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?

Two short sentences, zero filler, with the metrics and scope front-loaded before the default and the filtering hint. Nothing is redundant enough to cut, though the second sentence could be merged for tighter flow.

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 three-parameter read-only reporting tool with no output schema, the description covers the metric set, time basis, default window, and grouping level, which is enough to call it correctly. The absence of any hint about the returned structure (per-credential rows, charge units) is the remaining 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?

Schema coverage is 100%, so both date parameters and the username parameter are already documented with patterns and the exclusive/inclusive distinction. The description only restates the from-default and the username scoping, adding no format or interaction detail beyond the schema; baseline 3 applies.

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?

States the exact metrics (bandwidth bytes, request counts, wallet charges), the time basis (UTC date range), and the aggregation level (total and per credential). That is a specific resource+verb combination an agent can match to a need, though it does not name a sibling such as export_usage to sharpen the boundary.

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

Usage Guidelines3/5

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

Gives useful when-context (defaults to the current month) and a narrowing hint (use username to focus on one credential), but offers no exclusions or alternatives such as export_usage for full exports or get_balance for wallet-only queries. Usage is implied rather than directed.

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