Sleepwalker

Get Sleepwalker reports by URL

get_sleepwalker_reports_by_url

Read-onlyIdempotent

Find owned CI/AC tests by URL and fetch their latest UI-visible runs.

Input Schema

TableJSON Schema

Name	Required	Description
`url`	Yes	URL to search for in saved tests and reports.
`days`	No	Lookback window in days.
`limit`	No	Maximum number of items to return.
`test_type`	No	Optional report type filter. Use content_intelligence or ai_visibility.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedJun 28, 2026

addedInput schema / properties / days / description
```
Added value: +"Lookback window in days."
```

addedInput schema / properties / limit / description

Added value: +"Maximum number of items to return."

addedInput schema / properties / test_type / description

Added value: +"Optional report type filter. Use content_intelligence or ai_visibility."

addedInput schema / properties / url / description

Added value: +"URL to search for in saved tests and reports."

First observedJun 28, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive. Description adds that it searches owned tests and fetches latest UI-visible runs, which is valuable behavioral context beyond annotations. No contradiction.

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?

Single sentence, front-loaded, no wasted words. Efficiently communicates core function.

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?

Covers essential purpose. With full schema and output schema (signal shows output schema exists), description is adequate. Minor omission: behavior when no results not mentioned, but not critical.

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

Parameters4/5

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

Schema has 100% coverage; description adds context about 'owned' tests and 'UI-visible' runs, supplementing parameter descriptions. Adds meaning 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?

Clearly states 'Find owned CI/AC tests by URL and fetch their latest UI-visible runs.' Provides specific verb (Find) and resource (owned CI/AC tests) and action (fetch runs). Distinguishes from sibling tools that create runs, get status, etc.

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?

Implies usage: when you have a URL and need to find tests and latest runs. But no explicit guidance on when to use vs alternatives or when not to use. Context is provided but not extensive.

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.