DoubleData MCP

Set traffic limits

set_traffic_limits

Idempotent

Cap how much traffic a credential can use by setting daily, weekly, monthly, or total MB limits; set a value to 0 to remove that limit and give agents or teammates a bounded budget.

Instructions

Cap how much traffic a credential may use. Values are MB; 0 removes that limit. Only the provided limits change. Useful to give an agent or teammate a bounded budget.

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": {
      "username": "<username>"
    },
    "name": "set_traffic_limits"
  }
}

Input Schema

Name	Required	Description	Default
`daily_mb`	No
`total_mb`	No
`username`	Yes
`weekly_mb`	No
`monthly_mb`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 9, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare idempotency and non-destructiveness, so the description does not need to. It still adds genuinely useful behavior: units are MB and '0 removes that limit', which is non-obvious and not in the schema. It omits what the response looks like and whether unspecified limits are truly untouched versus reset, though the latter is partly covered by 'Only the provided limits change'.

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?

Four short sentences, front-loaded with the core action, then units, then partial-update semantics, then a use case. Every sentence contributes new information with no filler.

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, idempotent mutation with no output schema and no parameter descriptions in the schema, the definition covers the essential semantics (units, 0 behavior, partial update). Missing are error/validation behavior and whether the tool requires an existing credential, which would fully close 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?

Schema description coverage is 0%, so the description must carry the burden. It successfully explains the unit (MB) and the 0-means-remove convention that applies to the four limit fields, but it leaves the relationship between daily/weekly/monthly/total limits and the username format constraint unexplained.

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 gives a specific verb and resource ('Cap how much traffic a credential may use'), which is clearly distinct from the read-only sibling get_traffic_limits. It stops short of naming that sibling explicitly, so the differentiation is implied rather than spelled out.

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?

'Useful to give an agent or teammate a bounded budget' hints at a scenario, but there is no explicit when-to-use guidance, no prerequisites (the credential must already exist), and no mention of get_traffic_limits as the way to inspect current values first.

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