Skip to main content
Glama

submit_work

Commit leased changes and submit them for sandbox validation: ready=true records the diff, runs checks, and merges on pass; ready=false saves a checkpoint. Changes outside leases are rejected.

Instructions

Commit your leased changes and submit them. ready: true submits the task: the diff is recorded and your task's checks run in the sandbox (at most 15 minutes); if they pass, the runner merges it; if one fails, fix it and submit again. Changes outside your leases reject the submission. ready: false only saves a checkpoint commit.

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": {
      "execution_id": "<execution_id>",
      "agent_token": "<agent_token>",
      "summary": "<summary>",
      "ready": "<ready>"
    },
    "name": "submit_work"
  }
}

Input Schema

NameRequiredDescriptionDefault
readyYes
summaryYesWhat you did: the commit message and the submission note.
agent_tokenYesThe agent token join_execution returned (once).
execution_idYesThe heads-down run (exe-…).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false), it discloses a 15-minute sandbox check window, that the runner merges on success, that failed checks require resubmission, and that changes outside leases reject the submission. That is meaningful added behavioral context. However, it does not say what the call returns while checks are running, and it does not explain that resubmitting after a merge is not idempotent, so this falls short of a 5.

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

Conciseness5/5

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

Four compact sentences, the primary action first, then the ready branch, then the failure loop, then the lease constraint. No filler; every clause carries operational information.

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?

With no output schema, the description still tells the agent what happens after the call: the diff is recorded, checks run for up to 15 minutes, the runner merges, and out-of-lease changes reject the submission. That is enough for an agent to invoke and react correctly.

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?

Schema coverage is 75%, and the description devotes the most space to ready, spelling out both its values and their downstream effects in detail. The other three parameters are documented in the schema itself. The description adds real meaning for the one parameter whose semantics go beyond a boolean, though it says nothing about how summary length or execution_id scoping affects the submission.

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 names specific verbs and resources – commit leased changes, record the diff, run checks, merge – and clearly separates the ready:true submission from the ready:false checkpoint. It does not explicitly distinguish itself from siblings such as submit_plan, which is the only thing keeping it from a 5.

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 states concrete conditions for each mode (ready:true submits and runs checks; ready:false only saves a checkpoint) and gives an explicit recovery path when checks fail: fix and submit again. It gives no guidance on when another tool, such as submit_plan or lease, is the better choice, so the alternative-tool dimension is missing.

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