Skip to main content
Glama

BRAINIAC Telecom Roaming Audit

Audit roaming charges

telecom-billing_roaming-charge-audit
Read-onlyIdempotent

Recalculate international roaming charges from caller-supplied usage, tariff rules, packages, country zones, and billed charges. A usage row is priced only when exactly one tariff matches. Missing or ambiguous tariffs are reported and never assumed. Daily-pass packages zero incremental usage. Positive actual-minus-expected deltas form estimated overbilling by currency. No FX conversion is applied. Price $0.04 USDC. POST /api/v1/telecom-billing/roaming-charge-audit. An unpaid call returns the x402 payment terms and does not run.

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": {
      "usage": "<usage>",
      "billed_charges": "<billed_charges>"
    },
    "name": "telecom-billing_roaming-charge-audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
usageYesusage, array. Required.
zonesNozones, array. Optional.
tariffsNotariffs, array. Optional.
packagesNopackages, array. Optional.
billed_chargesYesbilled charges, array. Required.

Output Schema

NameRequiredDescriptionDefault
summaryNosummary. Object.
differencesNodifferences. Array.
explanationsNoexplanations. Array.
expected_chargesNoexpected_charges. Array.
duplicate_chargesNoduplicate_charges. Array.
allowance_violationsNoallowance_violations. Array.
estimated_overbillingNoestimated_overbilling. Array.
incorrectly_applied_rulesNoincorrectly_applied_rules. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: a usage row is priced only with exactly one matching tariff, missing or ambiguous tariffs are reported and never assumed, daily-pass packages zero incremental usage, positive deltas form estimated overbilling by currency, and no FX conversion is applied. It also states the price, endpoint, and unpaid-call behavior, which are all operationally important.

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?

The description is dense but well structured, starting with the core purpose, then pricing rules and edge cases, then payment and endpoint details. Every sentence adds useful information with no filler.

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

Completeness5/5

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

Given five top-level parameters, nested arrays, an output schema, and annotations, the description covers the key computation rules, error behavior, payment handling, and API endpoint. It is complete enough for an agent to invoke the tool correctly without needing further explanation.

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?

Schema description coverage is 100%, so the baseline is 3, but the description adds meaningful semantics about how usage, tariffs, packages, zones, and billed charges interact. It explains tariff matching and daily-pass package treatment, which goes beyond the generic schema field descriptions.

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?

The description immediately states a specific verb and resource: recalculate international roaming charges from caller-supplied usage, tariffs, packages, zones, and billed charges. It is precise enough that an agent can identify the tool's function without opening the schema.

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 description gives clear context for auditing roaming charges and includes important preconditions, such as unpaid calls returning x402 payment terms and not running. It does not explicitly state when to use this versus alternatives, but no sibling tools are present.

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