Skip to main content
Glama
Sign In

CallForMe

by tel.callforme
OverviewDiscussionsAdmin

Stop a call_around batch

stop_batch
DestructiveIdempotent

Stop dialing new places in a batch (e.g. the user already got what they needed). Calls in progress finish unless hang_up_active=true.

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": {
      "batch_id": "<batch_id>"
    },
    "name": "stop_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
batch_idYesThe batch_id from call_around
hang_up_activeNotrue also hangs up calls already in progress, cutting off anyone mid-answer and still billing those calls. Use it only when the user asks to end the calls now; default false lets them finish

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / hang_up_active / description
      Previous value: -"true also hangs up calls already in progress; default false lets them finish"New value: +"true also hangs up calls already in progress, cutting off anyone mid-answer and still billing those calls. Use it only when the user asks to end the calls now; default false lets them finish"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: the default is a soft stop where in-progress calls complete, and only an explicit flag causes mid-call cutoffs. That distinction is the main thing an agent needs before calling and is not derivable from the annotations alone.

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?

Two tight sentences, front-loaded with the default behavior and followed by the exception. Every clause carries information an agent needs; nothing is padded.

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 mutation with no output schema, the description covers the key behavioral surface: what stops, what continues, and the conditional destructive path. Missing only minor items such as what the call returns or whether a stopped batch can be resumed, which are low-stakes here.

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%, and the schema already spells out `batch_id` provenance and the billing/cutoff consequences of `hang_up_active`. The description restates the flag's effect in narrative form but adds no syntax or format detail beyond the schema, so the baseline of 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?

The definition gives a precise verb and resource plus a scope qualifier: it stops *new dialing* in a batch rather than killing everything. The parenthetical 'e.g. the user already got what they needed' anchors the intent in user-facing terms. It does not explicitly name the sibling `hang_up` as the alternative for ending live calls, so it falls just short of full sibling differentiation.

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 supplies a concrete when-to-use trigger ('the user already got what they needed') and a when-to-use-the-flag condition ('only when the user asks to end the calls now'). It stops short of naming an alternative tool or stating a when-not-to-use case, but the context for invoking it is clear.

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

All CallForMe toolsInspect
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.

Resources