Skip to main content
Glama
okenjioxx

Roblox Executor MCP Server

by okenjioxx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Symmetrically encrypt data with crypt.encrypt

crypt-encrypt
Read-onlyIdempotent

Encrypt a plaintext string in Roblox using a Base64 key, optional IV, and cipher mode; returns ciphertext and IV used.

Instructions

Encrypt a string with the executor's crypt.encrypt(data, key, iv?, mode?). The key is a Base64 string (see crypt-generate-key). An optional Base64 initialization vector (iv) and an optional cipher mode (e.g. 'CBC', 'CTR') may be supplied; when omitted the executor picks/derives them. The function returns the ciphertext plus the iv actually used, both of which are reported. This is a pure, side-effect-free compute that runs entirely in-game. Requires crypt.encrypt; on an executor without it, it returns { error } instead of throwing. The call is pcall-guarded so a bad key/iv degrades to a clean error. Returns { ciphertext, iv } or { error }. Signature: { data: string, key: string, iv: string?, mode: 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
ivNoOptional Base64-encoded initialization vector; omit to let the executor derive one.
keyYesThe Base64-encoded symmetric key (see crypt-generate-key).
dataYesThe plaintext string to encrypt.
modeNoOptional cipher mode (e.g. 'CBC', 'CTR', 'CFB', 'OFB', 'ECB'); omit for the executor default.
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.3/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds substantial context: pure/side-effect-free in-game compute, pcall-guarded so bad key/iv degrades to a clean error, and returns { ciphertext, iv } or { error }. This is rich, non-redundant behavioral disclosure.

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 front-loaded and clear, but the entry is long: it restates the full signature (already in schema) and appends metadata lines (Phase, cost, idempotency, Safety, Produces, and an 'On failure' pointer) that partly duplicate annotations and structured data.

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 explains the return shape ({ ciphertext, iv } or { error }), error/degradation behavior, prerequisites, and the executor's fallback for omitted params. An agent has everything needed to call it correctly.

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 baseline is 3. The description notes Base64 key/iv, mode examples (CBC/CTR), and that the executor derives iv/mode when omitted, but most of this is already documented in the schema properties, so it adds only marginal value.

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+resource ('Encrypt a string with the executor's crypt.encrypt') and even gives the call signature. It is clearly distinguishable from siblings like crypt-decrypt, crypt-hash, and 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear context: a pure, side-effect-free compute that runs in-game, requires an active client, and depends on `crypt.encrypt` existing (returning { error } otherwise). It also routes to crypt-generate-key for obtaining the key. It doesn't contrast when to prefer this over crypt-decrypt or other crypto siblings, so no explicit exclusions.

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