Skip to main content
Glama

Create a job

create_job

Start an asynchronous job for a billable operation and receive a job_id to poll for completion.

Instructions

Create an asynchronous job for a billable operation. Returns a job_id to poll.

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": {
      "operation": "<operation>",
      "payload": "<payload>"
    },
    "name": "create_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNoNot supported here: leave it out and use the estimate tool to price a call.
payloadYes
operationYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.4.1
    • addedInput schema / properties / dry_run
      Added value: +{
      +  "default": null,
      +  "description": "Not supported here: leave it out and use the estimate tool to price a call.",
      +  "title": "Dry Run"
      +}
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not idempotent, not destructive, open-world), and the description adds genuinely new behavior: execution is asynchronous, the call is billable, and the result is a job_id that must be polled. It stops short of explaining failure modes or what happens to the job if polling never occurs, but it materially extends the annotations.

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 async/billable framing and the polling contract front-loaded. Nothing redundant or padded.

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?

An output schema exists, so the return value need not be explained, and the description correctly covers the async creation contract. However, with a nested free-form payload and an undocumented operation string, an agent still lacks enough to construct a valid call without trial and error.

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 33%, so the description needed to compensate and does not. The critical 'operation' parameter has no description and no enum, so an agent cannot tell what values are legal, and 'payload' is an unconstrained free-form object whose shape is only inferable from the operation name.

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 ('Create an asynchronous job') and narrows scope to 'a billable operation', which separates it from read-side siblings like get_job or list_history. It also hints at the follow-up path ('Returns a job_id to poll') without naming get_job explicitly.

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?

Usage is only implied: 'for a billable operation' plus the polling note suggests this is the entry point for long-running paid work, but the description never says when to prefer it over estimate or the synchronous siblings. No exclusions or prerequisites are stated in the description itself; the only routing guidance lives in the dry_run schema field.

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