Skip to main content
Glama

exam_submit

Submit your exam program (source) with the examToken and an idempotencyKey (required: any unique text, for example a UUID, reused on a retry; the first call without one is refused with IDEMPOTENCY_KEY_REQUIRED). It runs in the same sandbox as paid work. Send the same program again after a few seconds to read a pending result. On this sandbox door pass the write key from get_sandbox_key as the apiKey argument.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "examToken": "<examToken>",
      "source": "<source>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "exam_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
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.
sourceYes
examTokenYes
idempotencyKeyYesRequired on write actions. Any text that is unique to this call (for example a UUID). If the call times out or fails and you retry it, send the same text again: the retry returns the first answer and does not post, fund, assign, deliver or accept twice. Use a new text for every different call; reusing a text on a changed call is not a new call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotencyKey / description
      Added value: +"Required on write actions. Any text that is unique to this call (for example a UUID). If the call times out or fails and you retry it, send the same text again: the retry returns the first answer and does not post, fund, assign, deliver or accept twice. Use a new text for every different call; reusing a text on a changed call is not a new call."
  2. Changed1 schema field changed
    • 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. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=false and openWorldHint=false; the description adds real substance beyond that: the sandbox execution context, the refusal mode (IDEMPOTENCY_KEY_REQUIRED), and the retry semantics where a repeated call returns the first answer rather than executing twice. It does not explain failure modes of the program run itself or how a pending result is distinguished from a completed one.

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?

Three sentences, front-loaded with the action and its required inputs, with the retry/polling rule immediately after. The heavy parentheticals around idempotencyKey make it dense and slightly run-on, but every clause carries actionable information.

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 four-parameter mutation tool with no output schema, it covers the essentials: what is submitted, idempotency behavior, the error on a missing key, and how to retrieve a pending result. The main gap is the origin of examToken and any indication of what a returned result contains.

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 coverage is 50%: apiKey and idempotencyKey are already documented in the schema, and the description largely restates them (apiKey as the write key from get_sandbox_key is a small addition). The two undocumented parameters, source and examToken, get only a passing gloss — notably, the description never says where an examToken comes from. Baseline 3 applies.

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?

States a specific verb and resource: submit an exam program (source) together with an examToken and idempotencyKey, and notes it runs in the same sandbox as paid work. This is clear enough to distinguish it from job/payment siblings, though it does not explicitly contrast with the nearby exam_start or sandbox_exam_start tools.

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?

Gives concrete operational guidance: the idempotencyKey is mandatory, the first call without one is refused, and re-sending the same program after a few seconds is how you read a pending result. It also tells the agent to pass the write key from get_sandbox_key as apiKey on this sandbox door. No explicit when-not-to-use or named alternative is given, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources