Skip to main content
Glama

Start

tm_operation_start

Starts a tracked operation session by specifying its type, total steps, and details so progress and cancellation can be managed.

Instructions

Start (tm_operations). Operation lifecycle and session management.

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": "tm_operation_start"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmNoConfirm a destructive action (cancel) without elicitation.
detailsNoAdditional details (start).
total_stepsNoTotal steps (start).
operation_idNoOperation ID (get_progress/cancel/get_metrics).
operation_typeNoType of operation (start).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.4.7
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Confirm a destructive action (cancel) without elicitation.",
      +  "type": "boolean"
      +}
  2. Addedv3.3.1

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing on top of that: it does not say that starting returns an operation_id for later polling, that operations are asynchronous, or that the tool's schema also carries cancel/progress parameters. Notably the schema's confirm parameter mentions a destructive 'cancel' action, which the description never reconciles.

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

Conciseness3/5

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

It is short and front-loaded, but it is short because it says little: the second fragment is a generic category label that conveys no actionable information. No sentence is wasteful, but the second one barely earns its place.

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

Completeness2/5

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

The tool has five parameters, a nested details object, and an output schema, and it multiplexes start/get_progress/cancel/get_metrics semantics within one call surface. Against that complexity, two fragments give an agent no picture of the lifecycle it is entering or how to follow up once an operation id exists.

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 100%, so each of the five parameters is documented in the schema itself, establishing the baseline of 3. The description adds no meaning beyond that, and importantly it never clarifies that operation_type and total_steps belong to the start path while operation_id and confirm belong to other multiplexed actions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Start (tm_operations)" largely restates the tool name and title, and the addition "Operation lifecycle and session management" is a vague category label rather than a statement of what starting an operation does. Nothing distinguishes this from tm_operation_get_progress, tm_operation_cancel, or tm_operation_get_metrics, all of which live in the same lifecycle family.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no statement of prerequisites, and no naming of alternatives. The parenthetical "(tm_operations)" hints at a grouping but does not tell an agent which sibling to pick for progress, cancellation, or session listing.

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