Field Service Business Platform by Doing Work

quotes_create

Create a quote from lines the worker wrote. Lines are never filled in by AI. Optional: good, better, best options and optional lines the customer picks when signing.

Input Schema

Name	Required	Description
`tm`	No	Rush or open-ended work: the customer signs the rates, and invoices.createFromTm bills approved time and materials at them. Lines may then be empty.
`lines`	Yes
`job_id`	Yes
`options`	No	Good, better, best: 2 to 5 options the customer chooses one of when signing. Each needs its own lines.
`tax_rate_id`	No	Tax rate to charge (taxes.listRates). Leave out to use the shop default rate; null for no tax.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 3, 2026

addedInput schema / properties / tm

Added value: +{
+  "description": "Rush or open-ended work: the customer signs the rates, and invoices.createFromTm bills approved time and materials at them. Lines may then be empty.",
+  "properties": {
+    "cap_minor": {
+      "description": "Optional not-to-exceed amount. Billing stops there until a change order is approved.",
+      "type": "integer"
+    },
+    "hours_per_day": {
+      "description": "Hours that make one day on a day rate. Default 8.",
+      "type": "number"
+    },
+    "materials_markup_bps": {
+      "description": "Added to what the shop paid for materials, in basis points (2000 is 20%)",
+      "type": "integer"
+    },
+    "rate_minor": {
+      "description": "Price per worker per hour or day, in cents",
+      "type": "integer"
+    },
+    "rate_unit": {
+      "enum": [
+        "hour",
+        "day"
+      ],
+      "type": "string"
+    },
+    "rush_rate_minor": {
+      "description": "Optional higher rate for time the shop marks as rush",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "rate_unit",
+    "rate_minor"
+  ],
+  "type": "object"
+}

First observedNov 1, 2026

TDQS

B3.2/5.0

Behavior3/5

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

No annotations are provided, so the description must carry the behavioral burden. It usefully discloses that AI must not fill lines and that options and optional lines are customer-selectable, but it says nothing about permissions, whether the quote is created as a draft or sent state, side effects, or the response shape.

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?

Three short sentences are front-loaded with the core action and the critical AI constraint. There is minor redundancy in 'Optional... optional lines,' but the description contains no wasted bulk.

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 create mutation with nested objects, no annotations, and no output schema, the description covers the purpose and the AI-line rule but omits draft/send state, permissions, and return behavior. The rich schema descriptions help with fields, yet the overall definition remains incomplete for fully safe invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 60%: job_id and the top-level lines array lack schema descriptions, while nested line and option fields are well documented. The description adds useful meaning about worker-authored lines and good/better/best options, but it does not compensate for the undocumented top-level job_id/lines or explain tm and tax_rate_id.

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 opens with a specific verb and resource ('Create a quote') and adds the key constraint that lines come from the worker and are never AI-filled. It does not explicitly distinguish this from siblings such as quotes_draft or quotes_finishDraft, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives some implied context through worker-authored lines, optional options, and optional customer-selected lines, but never states when to use this tool versus quotes_draft or quotes_finishDraft. In a crowded quotes_* family, that omission leaves routing to inference.

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

All Field Service Business Platform by Doing Work tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?