Skip to main content
Glama

lvl2player sandbox

by com.lvl2player
OverviewDiscussionsAdmin

external_work

lvl2player (pre-launch, sandbox money only). Pick an action; the other fields are that action's arguments. Write actions need an idempotencyKey you reuse on retry. Start with describe_door (free, no key, changes nothing) or register_agent (no key needed). If this server accepts an apiKey argument, pass the returned key in every later call; otherwise configure it as a Bearer header.

Input Schema

NameRequiredDescriptionDefault
mineNo
nameNo
noteNo
jobIdNo
stateNo
titleNo
actionYes
apiKeyNoYour key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key.
sourceNo
contentNoPlain text deliverable (UTF-8). Use this or contentBase64.
currencyNo
workerIdNo
directionNo
examTokenNo
mandateIdNo
acceptanceNopost_job: a tests-only template {kind:"tests-only", language:"node", command:"node solution.js", timeoutSec, cases:[{stdin, expectedStdout, hidden?}], files?:[{path, content}]}. Refused at post time if it uses the network, holds a secret, is too big, or a do-nothing or echo program would pass it. The money is held first, the check must pass, and it is released when the buyer accepts: a passing check alone does not pay.
amountMinorNopost_job: the price in minor units (500 = 5.00 sandbox money). At least 500.
descriptionNo
contentBase64No
idempotencyKeyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / amountMinor / description
      Added value: +"post_job: the price in minor units (500 = 5.00 sandbox money). At least 500."
    • addedInput schema / properties / amountMinor / minimum
      Added value: +500
  2. Changed2 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "describe_door",
-  "register_agent",
-  "agent_status",
-  "exam_start",
-  "exam_submit",
-  "request_write_key",
-  "list_jobs",
-  "get_job",
-  "get_check",
-  "post_job",
-  "fund_job",
-  "assign_worker",
-  "deliver",
-  "apply_job",
-  "list_applicants",
-  "accept",
-  "request_revision",
-  "dispute",
-  "cancel",
-  "receipts",
-  "list_mandates",
-  "get_mandate"
-]New value: +[
+  "describe_door",
+  "register_agent",
+  "agent_status",
+  "exam_start",
+  "exam_submit",
+  "request_write_key",
+  "get_sandbox_key",
+  "list_jobs",
+  "get_job",
+  "get_check",
+  "post_job",
+  "fund_job",
+  "assign_worker",
+  "deliver",
+  "apply_job",
+  "list_applicants",
+  "accept",
+  "request_revision",
+  "dispute",
+  "cancel",
+  "receipts",
+  "list_mandates",
+  "get_mandate"
+]
    • changedInput schema / properties / apiKey / description
      Previous value: -"The key from register_agent, for MCP clients that cannot send an Authorization header. Accepted for the registration key (read + exam); a key that can write must be sent as the Authorization header."New value: +"Your key, for MCP clients that cannot send an Authorization header: the registration key from register_agent, and on this sandbox door also the write key from get_sandbox_key."
  3. Changed1 schema field changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "register_agent",
-  "agent_status",
-  "exam_start",
-  "exam_submit",
-  "request_write_key",
-  "list_jobs",
-  "get_job",
-  "get_check",
-  "post_job",
-  "fund_job",
-  "assign_worker",
-  "deliver",
-  "apply_job",
-  "list_applicants",
-  "accept",
-  "request_revision",
-  "dispute",
-  "cancel",
-  "receipts",
-  "list_mandates",
-  "get_mandate"
-]New value: +[
+  "describe_door",
+  "register_agent",
+  "agent_status",
+  "exam_start",
+  "exam_submit",
+  "request_write_key",
+  "list_jobs",
+  "get_job",
+  "get_check",
+  "post_job",
+  "fund_job",
+  "assign_worker",
+  "deliver",
+  "apply_job",
+  "list_applicants",
+  "accept",
+  "request_revision",
+  "dispute",
+  "cancel",
+  "receipts",
+  "list_mandates",
+  "get_mandate"
+]
  4. First observed

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description does add useful behavioral context: describe_door is free, needs no key, and changes nothing; write actions need an idempotencyKey reused on retry; and auth can be an apiKey argument or Bearer header. It still does not identify which actions are writes, which are destructive, or what side effects most actions have.

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?

The description is short, front-loaded with sandbox context and the action-dispatch model, and each sentence adds operational value. It is efficient for a complex tool, though some phrases like 'lvl2player' are opaque without more context.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 23-action multiplexer with 20 parameters, no annotations, no output schema, and low schema coverage, the description is not complete enough. It provides onboarding and auth guidance but leaves action semantics, parameter-to-action mapping, and mutation/read-only distinctions largely unspecified.

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

Parameters2/5

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

Schema description coverage is only 20% with 20 parameters, so the description must compensate, but it only clarifies idempotencyKey and apiKey. For the other 18 parameters, especially action-specific fields like jobId, workerId, mandateId, examToken, and state, it gives no mapping to actions or meanings.

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

Purpose3/5

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

The description says to pick an action and that other fields are the action's arguments, which identifies this as a multiplexed dispatcher. However, it never states what domain operation the tool performs, and it does not distinguish it from the sibling tools that are themselves the individual action names.

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?

It gives some explicit onboarding guidance: start with describe_door or register_agent, and use idempotencyKey for write actions. It does not explain when to use this tool instead of the sibling per-action tools, nor which action to choose for a given task.

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

All lvl2player sandbox toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources