Skip to main content
Glama

Create a job request

createJobRequest

Books a field-service work order into the dispatch pipeline using customer UUID and requested job dates with time periods.

Instructions

Create a job request

Books a field-service job — the work order that enters the dispatch & scheduling pipeline. Send the customer's UUID plus requested job_dates (date + morning/afternoon/evening periods, ideally offered from GET /job-requests/booking-windows), optional job_type_id (service catalog), skill_ids (required technician qualifications) and a free-text description. Quoting, technician/crew assignment and completion then advance the work order through the business's workflow.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
priorityNoScheduling priority. Optional; omitted bookings receive the business's default_priority setting (assignment settings, default p2). p0=emergency (interrupt-driven insert), p1=top (displaced only by p0), p2=standard, p3=deferrable (first candidate for displacement).
job_datesYesRequested date(s) + period(s) the customer wants the job. At least one, up to 12.
skill_idsNoUUIDs of the skills the customer desires for this job. Optional; up to 20.
x_timezoneNoCustomer IANA timezone (sent as the X-Timezone header)
customer_idYesUUID of an existing customer of this business to book the job for. Required.
descriptionNoFree-text description of the work requested. Optional; max 2000 chars.
job_type_idNoUUID of the job type to classify this job. Optional; null leaves the job unclassified.
sla_deadlineNoSLA deadline (business-local naive datetime, e.g. "2030-06-14T17:00:00"). Optional; ONLY valid together with priority=p1 — arms the auto-escalation clock (the job escalates to p0 as breach risk crosses the business's safety buffer). Must be in the future.
idempotency_keyNoUnique key making retries safe: a repeat send with the same key returns the original booking instead of creating a duplicate (sent as the Idempotency-Key header)
Behavior4/5

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

The description explains the job's lifecycle (entering pipeline, subsequent steps) beyond annotations (readOnlyHint=false, etc.). It does not contradict annotations and adds context about the work order advancement.

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?

The description is a single, well-structured paragraph with four sentences. It front-loads the action and resource, then lists key parameters and the workflow, with no redundant or unnecessary words.

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?

The description covers the tool's role, inputs, and flow adequately for a creation tool with 9 parameters and no output schema. It references a sibling tool (listJobRequestBookingWindows) for additional guidance.

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 100%, so baseline is 3. The description adds workflow context by relating job_dates to the booking-windows endpoint and explaining the overall process, enhancing understanding of parameter roles.

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 clearly states the action ('Create a job request') and the resource ('Books a field-service job'). It explicitly distinguishes the tool by placing the job in the 'dispatch & scheduling pipeline', differentiating it from sibling tools like confirmJobRequest or quoteJobRequest.

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?

The description specifies required inputs (customer's UUID, job_dates) and recommends using the booking-windows endpoint for period selection. It outlines the workflow (quoting, assignment, completion) but does not explicitly state when to avoid this tool or mention alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/crisphive/crisphive-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server