Skip to main content
Glama

Stop measuring a chat's earlier history

stop_history_preview
Idempotent

Stop measuring a chat's earlier history when the user asks. Before the first page of a chat not captured yet, the measure is canceled and its allowance place returned (result: canceled); after it, or on a captured chat, it stops and keeps what it counted (result: stopped), and nothing more is asked of the phone. start_history_preview with continue: true resumes a stopped one. A chat with nothing measuring answers result: nothing_to_stop. Pass a list of up to 100 chat_ids to stop several. Name the chat as for start_history_preview; phone may be omitted when the user has a single number.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "stop_history_preview"
  }
}

Input Schema

NameRequiredDescriptionDefault
phoneNoThe connected number, from list_connected_numbers. Omit it when the user has a single connected number.
chat_idNoThe chat, by the chat_id list_capturable_chats returns, or a list of 1–100 of them. Pass exactly one of chat_id, contact_phone and chat_name.
chat_nameNoThe chat, by its name exactly as list_capturable_chats returns it. Pass exactly one of chat_id, contact_phone and chat_name.
contact_phoneNoThe chat, when it is a 1:1: the other party's number in E.164. Pass exactly one of chat_id, contact_phone and chat_name.

Output Schema

NameRequiredDescriptionDefault
resultNostopped | canceled | nothing_to_stop
statusNoThe measure's status after this call.
resultsNoBatch only: one per distinct chat_id, in input order.
next_stepNo
estimate_idNo
messages_seenNoWhat the measure counted, when it counted any.
reached_back_toNoThe earliest local day it reached.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: it explains the canceled versus stopped outcomes, what happens to the allowance and counted data, that nothing more is asked of the phone, and the nothing_to_stop result. This is a state-dependent mutation, and the description makes its behavior transparent without contradicting the non-destructive, idempotent annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and the paragraph is dense but largely earns its space by covering state-dependent results and resumption. It could be clearer with structure, but it does not contain obvious 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?

For a tool with complex state-dependent outcomes, the description covers the relevant cases: stopping before or after capture, already captured chats, nothing measuring, resuming via start_history_preview, and batching. With an output schema present, it is complete enough for an agent to select and invoke the tool correctly.

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 already 100%, and the input schema documents phone, chat_id, chat_name, and contact_phone thoroughly. The description mostly restates the batch limit and phone omission rule from the schema, adding only the cross-reference that the chat should be named as for start_history_preview.

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 states a specific verb and resource: stopping measurement of a chat's earlier history. It also names the sibling start_history_preview and explains that resuming uses that tool, so an agent can distinguish the stop action from the start action.

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 clear context for use: when the user asks to stop measuring history, and notes that start_history_preview with continue: true resumes a stopped measurement. It does not explicitly exclude stopping live capture or other stop operations, but the primary usage context is clear.

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