Roblox Executor MCP Server

Overview Schema Source Related Servers Discussions Admin

Clear all remote spy logs

clear-remote-spy-logs

Delete all captured remote spy logs from Roblox game clients to reset the logging session. Requires remote spy logging to be active first.

Instructions

Clear all captured Cobalt remote spy logs. Requires ensure-remote-spy first.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 29, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full burden. It indicates the tool clears logs but does not disclose potential side effects (e.g., irreversibility, permission requirements). While the operation is simple, the description could be more transparent about the destructive nature.

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 consists of two short sentences with no redundant information. Every sentence serves a purpose: stating the action and noting a prerequisite. It is efficiently written.

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?

Given no parameters and no output schema, the tool is simple. The description covers the purpose and prerequisite. However, it does not mention that logs are permanently deleted or that the operation is irreversible, which would add completeness. Still, it is mostly complete for a clear action.

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?

The input schema has no parameters, and schema coverage is 100% (trivially). The description does not need to add parameter details because there are none. A baseline of 4 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 clearly states the verb 'Clear' and the resource 'all captured Cobalt remote spy logs'. It distinguishes itself from siblings like 'get-remote-spy-logs' (retrieval) and 'ensure-remote-spy' (setup), making the tool's purpose unambiguous.

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 explicitly mentions a prerequisite: 'Requires ensure-remote-spy first.' This provides clear context for when this tool should be used. However, it does not mention when not to use it or provide alternative approaches, but for a straightforward clear operation this is sufficient.

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