Skip to main content
Glama

Create Job Tool

create-job
Idempotent

Creates one job directly in the selected FieldRobin business when the connection has job-write permission. Resolve the customer first and pass the verified customer ID when one is named. Use to create job in the connected business. Returns capability, status, approval_required, persisted, agent_run_id, scope, job, result, idempotent_replay, message.

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": {
      "title": "<title>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create-job"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYesShort job title.
statusNoInitial job status.
customer_idNoVerified customer ID, if the job belongs to an existing customer.
descriptionNoReadable issue and service description.
location_idNoBusiness location for the job.
voice_notesNoOptional internal voice-note text.
scheduled_atNoOptional local wall-clock appointment date/time or ISO timestamp with offset.
total_amountNoOptional quoted amount.
idempotency_keyYesOpaque retry key. Reuse it only for the same request to receive the verified result without creating a duplicate.
service_addressNoService address, if known.
appointment_countNoOptional appointment count.
technician_user_idNoVerified technician user ID, if assigned.

Output Schema

NameRequiredDescriptionDefault
jobYesSafe projection of the created record.
scopeYesBusiness boundary used to authorize this result.
resultYesVerified domain result and tenant-scoping evidence.
statusYesAuthoritative mutation outcome.
messageYesHuman-readable completion message.
persistedYesWhether the record was persisted.
capabilityYesExecuted domain capability name.
agent_run_idYesAuditable agent run identifier.
approval_requiredYesWhether additional approval is required.
idempotent_replayYesTrue when this repeats an already verified request.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "agent_run_id": {
      +      "description": "Auditable agent run identifier.",
      +      "type": "integer"
      +    },
      +    "approval_required": {
      +      "description": "Whether additional approval is required.",
      +      "type": "boolean"
      +    },
      +    "capability": {
      +      "description": "Executed domain capability name.",
      +      "type": "string"
      +    },
      +    "idempotent_replay": {
      +      "description": "True when this repeats an already verified request.",
      +      "type": "boolean"
      +    },
      +    "job": {
      +      "description": "Safe projection of the created record.",
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable completion message.",
      +      "type": "string"
      +    },
      +    "persisted": {
      +      "description": "Whether the record was persisted.",
      +      "type": "boolean"
      +    },
      +    "result": {
      +      "description": "Verified domain result and tenant-scoping evidence.",
      +      "type": "object"
      +    },
      +    "scope": {
      +      "description": "Business boundary used to authorize this result.",
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Authoritative mutation outcome.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "capability",
      +    "status",
      +    "approval_required",
      +    "persisted",
      +    "agent_run_id",
      +    "scope",
      +    "job",
      +    "result",
      +    "idempotent_replay",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-destructive, idempotent, closed-world semantics, so the description only needed to add on top; it does so by disclosing the write-permission requirement and the need to verify the customer before writing. The remaining behavior details (approval workflow implied by approval_required, duplicate-key errors) are left unexplained, but the auth/permission disclosure is the key value add.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The permission and resolved-customer prerequisites are front-loaded, which is good. But "Use to create job in the connected business" is a tautology restating the name, and the trailing enumeration of eleven return fields is wasted text given an output schema exists.

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?

For a 12-parameter mutation with an output schema, the core essentials (auth requirement, customer verification, idempotency) are present. Gaps remain around what approval_required/persisted mean for a normal caller and what happens on an idempotency-key mismatch, which the field list implies but never explains.

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 the baseline is 3; the description earns a step up by adding semantics the schema does not carry — that customer_id must be a previously verified ID and that only named customers should be resolved. Everything else (status enum, idempotency_key retry semantics) is already documented in the schema.

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?

"Creates one job directly in the selected FieldRobin business" gives a specific verb and resource with scope, which is easy to tell apart from create-customer or get-job by name. It stops short of explicitly contrasting with a sibling that might also produce jobs (e.g. quote/lead conversion), so it is clear but not fully differentiated.

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 states a real precondition (connection must have job-write permission) and a workflow prerequisite (resolve the customer first and pass the verified customer ID when one is named). There is no when-not guidance or named alternative, but the context for when to reach for this tool is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources