Skip to main content
Glama

Sleepwalker

by ai.sleepwalker
OverviewDiscussionsAdmin

Get Sleepwalker visibility run status

get_sleepwalker_visibility_run_status
Read-onlyIdempotent

Read status, probe progress, and optional results for a queued infrastructure AI Visibility run.

Poll compact status while queued or running. Set include_results only after completion or when the user explicitly needs full response and citation data. For large runs, page with results_offset/results_limit (ca_result reports results_total), or fetch one answer at a time with get_sleepwalker_prompt_response; the summary always covers the full run.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
run_idYesSleepwalker run ID returned by a create or list tool.
results_limitNoWith include_results, return at most this many results. Omit for all. Use with results_offset to page large runs; results_total in ca_result reports the full count.
include_probesNoInclude probe-level progress for an AI Visibility run.
results_offsetNoWith include_results, skip this many results (paging for large runs).
include_resultsNoInclude full AI responses and citations. Prefer false while polling queued or running work.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / results_limit
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "With include_results, return at most this many results. Omit for all. Use with results_offset to page large runs; results_total in ca_result reports the full count.",
+  "title": "Results Limit"
+}
    • addedInput schema / properties / results_offset
      Added value: +{
+  "default": 0,
+  "description": "With include_results, skip this many results (paging for large runs).",
+  "title": "Results Offset",
+  "type": "integer"
+}
  2. Changed3 schema fields changed
    • addedInput schema / properties / include_probes / description
      Added value: +"Include probe-level progress for an AI Visibility run."
    • addedInput schema / properties / include_results / description
      Added value: +"Include full AI responses and citations. Prefer false while polling queued or running work."
    • addedInput schema / properties / run_id / description
      Added value: +"Sleepwalker run ID returned by a create or list tool."
  3. First observed

TDQS

A5/5.0
Behavior5/5

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

Annotations confirm readOnly, idempotent, non-destructive. Description adds polling behavior, result paging with ca_result reports results_total, and that summary covers full run. No contradictions.

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 sentences, front-loaded with main purpose, then usage guidance. No redundant or vague statements. Every sentence adds essential information.

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?

Given complexity (5 params, 1 required) and presence of output schema, description covers polling, paging, include_results usage, and alternative tool. No missing context needed for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

100% schema coverage, but description adds value by explaining when to use include_results (only after completion), paging with results_offset/results_limit, and referencing ca_result. Also mentions alternative tool for single answers.

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?

Clear verb 'Read' with specific resources 'status, probe progress, and optional results' for an AI Visibility run. Distinguishes from sibling tools like get_sleepwalker_content_run_status and get_sleepwalker_prompt_response by focusing on run-level status.

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

Usage Guidelines5/5

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

Provides explicit guidance: poll compact status while queued/running, set include_results only after completion or when full data needed, page large runs with offset/limit, and mentions alternative get_sleepwalker_prompt_response for individual answers.

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

All Sleepwalker toolsInspect
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.

Resources