Skip to main content
Glama

Create a job request

createJobRequest

Book a field-operations job into the dispatch and scheduling pipeline by sending the customer UUID plus requested date/time periods; add optional skills and job type to direct assignment.

Instructions

Create a job request

Books a field-operations 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)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already signal this is a mutable, non-destructive operation. The description adds meaningful behavioral context: the created work order enters the dispatch & scheduling pipeline, and quoting/assignment/completion follow. This goes beyond the bare mutation hint and helps the agent understand side effects and lifecycle.

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?

The substantive description is compact and front-loaded with the core action. The only minor waste is the opening line 'Create a job request', which simply repeats the title. Otherwise every sentence earns its place.

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?

Given the 9-parameter schema with full descriptions, the tool description adds the most valuable missing context: the scheduling-pipeline placement and the workflow stages that follow. It does not describe the response shape, but with no output schema that is a minor gap for a creation operation whose schema is already thorough.

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 description coverage is 100%, so the schema carries the full parameter documentation. The description adds useful selection guidance beyond the schema, particularly the recommendation to source job_dates from GET /job-requests/booking-windows and the note that skill_ids represent required technician qualifications.

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 opens with a specific verb and resource: 'Books a field-operations job — the work order that enters the dispatch & scheduling pipeline.' This clearly differentiates createJobRequest from sibling read/update/confirm/quote tools and states exactly what object is being created.

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 gives concrete guidance on what to send and even points to the booking-windows endpoint as the ideal source for job_dates. It does not explicitly name alternatives or say 'use quoteJobRequest instead when...', but it implies quoting is a downstream step, which helps an agent route correctly.

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

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