Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Base64-decode a string via the executor crypt library

crypt-base64-decode
Read-onlyIdempotent

Decode a Base64 string back to raw bytes in the Roblox client using the executor's crypt library. Returns { decoded } or a clean error; pcall-guarded.

Instructions

Decode a Base64 string back to its raw bytes using the executor's crypt library. This is a pure, side-effect-free compute that runs entirely in-game. The decoder probes BOTH the flat form (crypt.base64decode) and the namespaced form (crypt.base64.decode), using whichever the executor provides. Requires a crypt table; on an executor without it (no crypt, or no base64 decoder under either name) it returns { error } instead of throwing. The call is pcall-guarded so malformed Base64 degrades to a clean error. Returns { decoded } or { error }. Signature: { data: string, threadContext: number?, timeoutMs: number? }. Phase: observe; cost=medium; idempotency=read-only. Requires: active-client. Produces: structured-result. Safety: read-only. On failure: inspect tool-schema for exact fields, defaults, constraints, and an invocation example.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesThe Base64-encoded string to decode.
timeoutMsNoOptional per-call deadline in milliseconds; omit it to use the tool or server default.
threadContextNoOptional Roblox thread identity for this call; omit it to use the server default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0-spies.2

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations by disclosing that the decoder probes both flat and namespaced forms, requires a crypt table, returns { error } rather than throwing when crypt is absent, and is pcall-guarded so malformed Base64 degrades to a clean error. This is exactly the runtime behavior an agent needs.

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

Conciseness4/5

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

Front-loads the core operation and error-handling semantics well. It is slightly padded with trailing metadata (Phase/cost/idempotency/safety restated alongside annotations) and a generic 'On failure: inspect tool-schema' boilerplate sentence.

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?

Despite no output schema, the description specifies the return shapes ({ decoded } or { error }), the failure behavior, and the executor dependency, leaving nothing essential missing for correct invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents data, timeoutMs, and threadContext with meaning. The description repeats the signature but adds no syntax or format detail beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb (decode) and resource (Base64 string to raw bytes) plus the exact library used (executor's crypt library). It is immediately distinguishable from the sibling crypt-base64-encode.

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?

The description establishes context (pure, side-effect-free, runs in-game) but never states when to prefer this tool over alternatives or when it is inapplicable. Usage is implied by the operation rather than explicitly spelled out.

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