Roblox Executor MCP Server

Overview Schema Source Related Servers Discussions Admin

Ensure the Cobalt remote spy is loaded

ensure-remote-spy

Load or verify Cobalt remote spy in the active Roblox client before reading, clearing, blocking, or ignoring remote spy logs.

Instructions

Load or verify the Cobalt remote spy in the active Roblox client. Call before reading, clearing, blocking, or ignoring remote spy logs.

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": "ensure-remote-spy"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 29, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries full burden. It discloses that the tool loads or verifies the spy, implying it may initialize if not loaded. While it doesn't detail error handling or idempotency, the simplicity of the tool (0 parameters) makes this acceptable. 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?

Two short sentences, front-loaded with the action, no extraneous words. Every sentence adds value: first states purpose, second gives usage context.

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 zero parameters, no output schema, and the tool's simple role as a prerequisite for remote spy operations, the description is fully adequate. It explains what it does and when to call it.

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?

There are zero parameters. Schema description coverage is 100% (trivially). The rubric states '0 params = baseline 4', so this score is appropriate.

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 specifies the action ('Load or verify') and resource ('Cobalt remote spy in the active Roblox client'). It distinguishes from sibling tools like get-remote-spy-logs and block-remote by explicitly stating it is a prerequisite for operations like reading, clearing, blocking, or ignoring remote spy logs.

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?

The description provides clear when-to-use guidance: 'Call before reading, clearing, blocking, or ignoring remote spy logs.' It does not explicitly state when not to use or list alternatives, but the context is sufficient for this tool's role.

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