Skip to main content
Glama

studio_dispatch_job

Dispatches an operator-approved job through a configured local upstream and blocks retries after uncertain submissions so they can be manually reconciled.

Instructions

Dispatch only an operator-approved job via a configured local upstream. On uncertain submission, block retries for manual reconciliation.

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": {
      "jobId": "<jobId>",
      "toolName": "<toolName>",
      "toolArguments": "<toolArguments>"
    },
    "name": "studio_dispatch_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
jobIdYes
toolNameYes
toolArgumentsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3.1/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 behavioral burden and does disclose meaningful traits: a precondition (operator approval), an environmental dependency (configured local upstream), and a non-idempotent retry hazard with a manual reconciliation fallback. It still omits permission/auth requirements, whether a successful dispatch is idempotent, and what a successful submission returns.

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?

Two tightly packed sentences with the precondition front-loaded and the failure-mode rule second; no filler. Minor cost is that 'configured local upstream' is left unexplained, which is under-specification rather than verbosity.

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?

This is a mutating dispatch tool with three required params, a nested arguments object, no annotations, and no output schema, so the description should carry far more. It covers safety and retry semantics reasonably but leaves the entire input contract and the meaning of the nested arguments undocumented.

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 0% across three required parameters, including a nested free-form 'toolArguments' object, so the description is the only place parameter meaning could be supplied. It says nothing about jobId, toolName, or the shape/purpose of toolArguments, leaving the agent to guess how a job is identified and what tool is actually being invoked.

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 uses a specific verb ('dispatch') and resource ('job'), and narrows scope with two qualifiers: the job must be operator-approved and must go through a configured local upstream. That is far more informative than the bare name studio_dispatch_job, though it does not explicitly contrast itself with siblings such as studio_plan or studio_preflight.

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?

'Dispatch only an operator-approved job' gives an implicit precondition for use, and 'block retries for manual reconciliation' tells the agent what to do on an uncertain submission. However, no alternative tools (preflight, plan, failure recording) are named, and the description never says what to do instead when the approval precondition is unmet.

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