CallMCP — Phone Call MCP Server

Set Automatic Collection

agency_billing_set_automatic_collection

DestructiveIdempotent

Turns monthly automatic collection of wholesale charges on or off under the accepted terms. Requires the agency owner and accepted terms; it cannot be turned off while any client is on an active partner plan. It charges nothing by itself.

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

Input Schema

Name	Required	Description	Default
`accepted`	Yes	true to authorize automatic monthly collection, false to stop it.
`partnerId`	Yes	The agency (partner) workspace ID.

Output Schema

Name	Required	Description
`error`	No	Present when success is false
`receipt`	No
`success`	Yes	Whether the tool completed successfully

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 12, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already flag destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is partly covered. The description adds context the annotations cannot: the owner-level authorization requirement and the precondition that blocks disabling while a client sits on an active partner plan. 'It charges nothing by itself' usefully bounds what 'destructive' means here, though the effect on already-scheduled collections is not spelled out.

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 what the tool does, then prerequisites, then the constraint and a scope clarification. Every sentence adds information and none restates the title or schema.

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 two-parameter toggle with full schema coverage, annotations and an output schema, the description covers purpose, authorization, preconditions and the limits of the destructive effect. The only gap is what happens to in-flight or scheduled collections when it is switched off, a minor omission given the supporting structured fields.

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 coverage is 100%, so the baseline would be 3. The description earns above that by attaching a concrete condition to the accepted=false path: it cannot be turned off while any client is on an active partner plan. That is parameter-level meaning the schema does not carry.

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 states a specific verb and resource: toggling monthly automatic collection of wholesale charges on or off. That is far more precise than the name alone and an agent can tell it apart from setup-oriented siblings like agency_billing_setup_collection. It stops short of naming a sibling or explaining the distinction, so it is clear but not fully differentiated.

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?

It gives real operating context: the caller must be the agency owner, terms must be accepted, and the off-direction is blocked while any client is on an active partner plan. That is enough to know whether the call is permissible. It does not explicitly compare itself to agency_billing_setup_collection, which is the main sibling an agent could confuse it with.

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

All CallMCP — Phone Call MCP Server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.