Skip to main content
Glama

cancel_research

Cancel an in-flight Fast Research run for a notebook by sending a cancellation request; verify the result with research_sources.

Instructions

Cancel an in-flight Fast Research run for a notebook. RPC-backed. Fire-and-forget: the server does not validate the run id, so cancelled: true means the cancel was sent; confirm with research_sources. run_id defaults to the notebook’s current research task.

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

Input Schema

NameRequiredDescriptionDefault
run_idNoThe research task id (as research_sources returns). Defaults to the current task.
notebook_idNoNotebook UUID (alternative to notebook_url).
notebook_urlNoNotebookLM notebook URL.

Output Schema

NameRequiredDescriptionDefault
dataNoThe tool payload on success. The exact shape depends on the tool.
errorNoHuman-readable error message, present only when success is false.
successYesWhether the tool call succeeded.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv4.9.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does so well: it discloses RPC backing, fire-and-forget semantics, that the server does not validate the run id, and that `cancelled: true` only means the cancel was dispatched. Left out are auth requirements and behavior for already-finished or unknown runs.

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 dense, front-loaded sentences with zero filler: scope first, then transport, then the critical caveat. Every clause carries information an agent needs before calling.

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?

Output schema exists, so return values need not be explained, and the description still clarifies what `cancelled: true` actually means. Combined with zero required parameters and full schema coverage, the only gap is auth and failure-mode behavior.

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 the schema already documents run_id, notebook_id and notebook_url. The description adds only the defaulting behavior for run_id (current research task), which largely restates the schema. Baseline 3 applies.

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?

States a specific verb and resource: 'Cancel an in-flight Fast Research run for a notebook.' The 'Fast Research run' scope plus the pointer to research_sources for confirmation lets an agent tell this apart from cancel_answer without opening any schema.

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?

Explains the operating context (in-flight runs) and gives concrete post-call guidance: confirm the cancel with research_sources. It also notes run_id defaults to the notebook's current task, so an agent knows the zero-argument path is valid. No explicit when-not or auth prerequisites are given.

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