Skip to main content
Glama
Sign In
Scout

Scout

by Lautrek
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

scout_handoff_cancel

Cancel a pending handoff and remove the browser banner using the handoff ID from scout_handoff.

Instructions

Cancel a pending handoff and remove the banner from the browser.

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": {
      "handoff_id": "<handoff_id>"
    },
    "name": "scout_handoff_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
handoff_idYesThe handoff_id returned by scout_handoff

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the burden. It states cancellation and banner removal, but does not disclose error scenarios (e.g., invalid handoff_id, handoff already completed) or whether the operation is idempotent.

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?

The description is a single sentence with no wasted words. Every part is informative and front-loaded.

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 tool with one parameter and no output schema, the description covers the core action and result. Lacks error handling info but is largely 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 100% with a clear description for handoff_id. The description adds no further semantic value beyond the schema.

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 clearly states the action ('Cancel') and the resource ('pending handoff'), and adds the specific effect ('remove the banner from the browser'). It distinctly separates from sibling tools like scout_handoff (initiate) and scout_handoff_check (check status).

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?

No explicit guidance on when to use this tool versus alternatives (e.g., waiting for handoff to complete or checking status first). The context implies it is for cancellation, but not stated explicitly.

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