Skip to main content
Glama

Request the booking.

request_booking

Request the booking. Idempotent per job; requires approve:true (types-name-as-signature approval of the inventory + quote, stored with a quote snapshot) and accept_terms when the mover has terms. Scope: jobs:write.

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": {
      "job_id": "<job_id>",
      "name": "<name>",
      "email": "<email>",
      "approve": "<approve>"
    },
    "name": "request_booking"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe submitted name is the signature on the approval.
emailYes
esignNoMust be true unless already given with the contact details: the customer agrees to electronic documents and signing
phoneNo
job_idYesThe job id (ULID)
approveYesMust be true: approves the inventory as complete and this quote. Cleared if the inventory is edited afterwards.
accept_termsNoRequired (true) when the job's `terms.terms` is non-null
publications_receiptNoMust be true on an interstate quote the mover sent: the customer received the two federal moving publications

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / esign
      Added value: +{
      +  "description": "Must be true unless already given with the contact details: the customer agrees to electronic documents and signing",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / publications_receipt
      Added value: +{
      +  "description": "Must be true on an interstate quote the mover sent: the customer received the two federal moving publications",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation, so the bar is lower. The description still adds genuinely new behavioral context: idempotency keyed on the job, that the approval and a quote snapshot are persisted together, and that the call operates under the jobs:write scope. It stops short of saying what a successful request triggers (mover notification, booking state change), but that is a minor gap.

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?

Two sentences, front-loaded with the action and then the hard preconditions, with no filler. The parenthetical stack of requirements makes the second sentence dense and slightly run-on, but every clause carries information an agent needs before calling.

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?

For a non-idempotent-looking mutation with eight parameters, no output schema, and no nested objects, this covers the essentials: idempotency, authorization scope, signature semantics, and conditional requirements. What is missing is the post-call consequence (what state the job moves to, whether external parties are notified), which an agent would want before committing a customer's booking.

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?

At 75% schema coverage the schema does most of the work, documenting name-as-signature, approve, accept_terms, and publications_receipt individually. The description reinforces the cross-field relationship (approve is a typed-name signature over the inventory and quote, stored with a snapshot) which is not obvious from the single-parameter descriptions. It says nothing about esign, phone, or email, so it only partly compensates for the uncovered quarter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence restates the title verbatim, and 'request the booking' is not pinned down concretely (submitting to the mover? creating a booking record?). The follow-on clauses do add real scope - an approval plus quote snapshot is captured - but the definition never distinguishes this action from siblings like submit_job, quote_inventory, or approve_inventory, so an agent cannot route on purpose alone.

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?

Preconditions are stated well: approve must be true, accept_terms when the mover has terms, and the schema adds the interstate publications_receipt case. However these are requirements rather than when-to-use guidance - there is no statement of when this tool should be called instead of quote_inventory, approve_inventory, or submit_job, nor any exclusion for jobs already booked.

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