Skip to main content
Glama

clawbridge_submit

Record an idempotent development task for a registered project, storing it as queued so dispatch can start its worker.

Instructions

Record an idempotent development task for a registered project. Submit stores it as queued; call clawbridge_dispatch to start its worker.

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": {
      "projectId": "<projectId>",
      "spec": "<spec>",
      "idempotencyKey": "<idempotencyKey>"
    },
    "name": "clawbridge_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
specYes
modelNo
projectIdYes
idempotencyKeyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: idempotency, persistence in a 'queued' state, and the prerequisite of a registered project. It stops short of explaining what happens on a repeated idempotency key, permission or registration failure modes, or what the caller gets back.

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?

Two sentences, zero filler, with the lifecycle constraint front-loaded before the follow-up action. Nothing is repeated from the schema and nothing needs trimming.

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

Completeness3/5

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

The tool has four parameters, no annotations, no output schema, and no schema descriptions, so the description should also hint at the return value (e.g., a task identifier or queued status) and at duplicate-key behavior. It covers the lifecycle adequately but leaves those gaps for a mutation tool with no structured support.

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 0% across four parameters, so the description must compensate. 'Idempotent' and 'registered project' implicitly explain idempotencyKey and projectId, and 'development task' hints at spec, but the model parameter is never mentioned and no parameter gets format, constraint, or uniqueness semantics.

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?

The description names a specific verb and resource ('Record ... a development task for a registered project') and immediately scopes it as queued-only, explicitly routing worker startup to clawbridge_dispatch. An agent can distinguish this from the dispatch sibling without opening either schema.

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 a clear next step ('call clawbridge_dispatch to start its worker'), which implies the when-to-use context of queueing work. However, it offers no explicit exclusions or comparison to alternatives such as clawbridge_cancel, clawbridge_tasks, or the codebuddy/workbuddy development starters, so the guidance is implied rather than stated.

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