Skip to main content
Glama

CallMCP — Phone Call MCP Server

Freeze Wholesale Billing Period

agency_billing_freeze_period
Idempotent

Calculates and locks the wholesale statement for one closed calendar month (UTC) from the agency's billable client intervals. Requires the agency owner. Freezing the same month again returns the same period; it does not charge.

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": {
      "partnerId": "<partnerId>",
      "start": "<start>",
      "end": "<end>"
    },
    "name": "agency_billing_freeze_period"
  }
}

Input Schema

NameRequiredDescriptionDefault
endYesFirst instant of the following UTC month (ISO date-time).
startYesFirst instant of the closed UTC month (ISO date-time).
partnerIdYesThe agency (partner) workspace ID.

Output Schema

NameRequiredDescriptionDefault
errorNoPresent when success is false
receiptNo
successYesWhether the tool completed successfully

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the mutation and repeatability profile is largely pre-supplied. The description does add value beyond them: the owner-permission requirement, what exactly gets locked (the statement, not the client intervals), and the reassurance that freezing does not charge. It says nothing about failure modes for non-owner callers or unclosed months.

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?

Three short sentences, front-loaded with the action and scope, then prerequisites, then the idempotency/no-charge caveat. No filler and nothing repeated from the tool name alone.

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?

Annotations plus an output schema mean the return shape and safety profile are covered elsewhere; the description supplies the operational context an agent needs (authorization, month must be closed, re-run safety). Only edge behavior - what happens when the month is not closed or the caller lacks the owner role — is left unstated.

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?

With schema_description_high (100%), the schema already documents partnerId, start and end including the UTC month boundary semantics. The description reinforces the month-scoping but adds no format, validation or edge-case detail beyond the schema. Baseline 3 is appropriate.

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 compound verb ('calculates and locks') plus the exact resource ('wholesale statement') and its scope ('one closed calendar month (UTC) from the agency's billable client intervals'). This is clearly distinguishable from sibling billing mutations like record_adjustment or set_plan without opening their schemas.

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?

Gives clear preconditions: the month must already be closed, the caller must be the agency owner, and re-freezing is a no-op. It does not name an alternative tool or state explicit when-not-to-use cases (e.g., open months), so it stops short of the 5 bar.

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.