Skip to main content
Glama
Sign In
Roblox Executor MCP Server

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Show which Roblox client this session targets

get-active-client
Read-onlyIdempotent

Report which live Roblox client this session resolves to and whether it is ambiguous or offline. Use it to confirm routing before running code across multiple games or after a rejoin.

Instructions

Report which live Roblox client THIS session currently resolves to (read-only), including its current selection and whether resolution is ambiguous or offline. Use it to confirm routing before running code, especially when multiple games are connected or after a rejoin. Signature: {}. Phase: observe; cost=low; idempotency=read-only. Requires: none. Produces: structured-observation. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

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": "get-active-client"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-spies.2

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered; the description restates it but also adds useful behavioral detail beyond the annotations, namely that the result reports current selection and can indicate ambiguous or offline resolution. The 'On failure: inspect tool-schema' pointer is also helpful.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded, but the trailing metadata block is partly redundant: 'idempotency=read-only' and 'Safety: read-only' restate the readOnlyHint/idempotentHint annotations, and 'Requires: none' is derivable from the empty schema. 'Phase: observe; cost=low' does add value, so the padding is moderate rather than severe.

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?

For a zero-argument read-only observation tool with no output schema, the description covers what it returns (client selection, ambiguity, offline state), when to reach for it, and where to look for field details, which is nearly everything an agent needs. Only the exact return shape is left to the tool-schema pointer.

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 tool takes zero parameters (baseline 4) and schema coverage is 100%, so there are no parameter semantics to explain. The empty 'Signature: {}' correctly signals a no-argument call.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: it reports which live Roblox client THIS session resolves to, including selection state and ambiguity/offline status. The phrase 'THIS session currently resolves to' implicitly separates it from list-clients and select-client, but no sibling is named explicitly, so it stops short of the top score.

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?

It gives a clear usage condition: 'Use it to confirm routing before running code, especially when multiple games are connected or after a rejoin.' That is concrete when-to-use context, but there is no explicit when-not guidance and no alternative tool (e.g. list-clients) is named.

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

Deploy Server

Other Tools