Skip to main content
Glama
Sign In
td-atlas

td-atlas

by grigabyte
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

td_timeline_cancel

Stop a running timeline job to revert crop and play mode while preserving written files. Use without specifying a job to stop the most recent one.

Instructions

Stop a td_timeline_run job now; the crop and the play mode go back.

Files already written stay. Without job, the latest one.

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

Input Schema

NameRequiredDescriptionDefault
jobNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral disclosure burden and does so well: it says the stop is immediate, crop and play mode revert, already-written files persist, and the latest job is used if 'job' is omitted. It leaves failure behavior unstated, but the key side effects are covered.

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 with no filler; the main action is front-loaded, and the default behavior and side effects are stated compactly. The slightly awkward phrasing does not reduce clarity.

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 simple cancel operation with one optional parameter, the description covers the immediate effect, persistence of files, and default target. The output schema can handle return-value details. It never states what happens if no job is running, but overall it is fairly complete.

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 0%, so the description is the only source of parameter meaning. It explains that 'job' identifies the run and that omitting it targets the latest one, which is helpful. However, it does not specify the expected format of the job identifier or how to discover valid job values.

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 clear verb ('Stop') and resource ('a td_timeline_run job'), making the tool's purpose obvious. It also distinguishes itself from the sibling run/status/profile tools by focusing specifically on cancellation.

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

Usage Guidelines3/5

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

The use case is clearly implied: cancel a td_timeline_run job. However, there is no explicit comparison to alternatives like td_timeline_status or td_timeline_run, nor any guidance on when not to use this tool.

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

Deploy Server

Other Tools