Sleepwalker

Cancel Sleepwalker visibility run

cancel_sleepwalker_visibility_run

DestructiveIdempotent

Cancel the queued remainder of an AI Visibility run (the killswitch).

Use when the user wants to stop a direct-URL run (created by create_sleepwalker_visibility_run) that is queued or running. Probes no worker has picked up yet never run and their reserved credits return to the account; probes a worker already claimed (they are dispatched in batches) finish and settle normally, and completed results stay available. While work is in flight the response reports billing_pending true and the remaining release normally happens when the last probe finishes; if a run later looks stuck (still running with nothing progressing, for example after a worker crash), call this tool again to force the remainder out and release the credits. Idempotent: cancelling a finished run, or cancelling twice, changes nothing and reports the current state. Poll get_sleepwalker_visibility_run_status for final counts; released credits equal reserved minus settled once terminal.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`run_id`	Yes	Sleepwalker run ID returned by a create or list tool.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedJul 15, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Description adds significant detail beyond annotations: explains effects on probes, credits, billing_pending, and idempotency. No contradiction with 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?

Description is longer but well-structured and informative. Each sentence adds value. Could be slightly more concise but still effective.

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?

Covers edge cases (stuck runs, multiple cancellations, final state), references status tool. With output schema present, return values are not needed. Complete for a mutation tool.

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% for the single parameter. Description doesn't add much beyond schema, but mentions run_id comes from create/list tools, which provides minimal extra context.

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 tool cancels a queued visibility run, using the 'killswitch' analogy. It distinguishes from siblings like create and status tools.

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?

Explicitly says when to use: to stop a direct-URL run that is queued or running. Provides scenarios for calling again. Lacks explicit when-not-to-use but context is clear.

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

All Sleepwalker tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.