Skip to main content
Glama

HireNimbus home services MCP

Book same pro again

book_same_pro_again

Creates a service request for a provider associated with a prior job ID. Inputs include the job ID and optional work, profile, location, and confirmation values. Requires authentication. Unauthenticated requests return status "auth_required". confirm_booking=false returns a preview; confirm_booking=true submits the request. Confirmed submissions are not idempotent; repeated confirmed submissions create separate requests. Returns booking status, summary, identifiers, links, and notification statuses.

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": "book_same_pro_again"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoOptional name override; the authenticated homeowner profile supplies the value otherwise
phoneNoOptional phone override; the authenticated homeowner profile supplies the value otherwise
job_idYesIdentifier of the prior job
sourceNoAI Assistant
addressNoOptional street-level address override. The profile or prior-job address is used otherwise. Accepted structured fields include address1, city, region, postalCode, etc.; formattedAddress is output only.
contextNoOptional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
locationNoOptional geocoding hint when address lacks coordinates. Accepted forms are lat+lng, zip, or text.
confirm_bookingNofalse (default) returns a rebooking preview without submitting. true submits the rebooking.
job_descriptionNoDescription of the new work; the prior job description is reused when absent

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed13 schema fields changed
    • changedInput schema / $defs / BookingLocationInput / description
      Previous value: -"Optional geocoding hint when the address lacks coordinates. Provide one style only."New value: +"Optional geocoding hint for addresses without coordinates, in one supported form."
    • changedInput schema / $defs / BookingLocationInput / properties / lat / description
      Previous value: -"Latitude; use together with lng or lon"New value: +"Latitude; paired with lng or lon"
    • changedInput schema / $defs / BookingLocationInput / properties / lng / description
      Previous value: -"Longitude; use together with lat"New value: +"Longitude; paired with lat"
    • changedInput schema / $defs / BookingLocationInput / properties / lon / description
      Previous value: -"Alias for lng when paired with lat"New value: +"Longitude alias; paired with lat"
    • changedInput schema / $defs / HomeownerAddressInput / description
      Previous value: -"Street-level address override for booking tools. Omit to use the authenticated profile address."New value: +"Optional street-level address override; the authenticated profile address is used otherwise."
    • changedInput schema / properties / address / description
      Previous value: -"Optional street-level address override. Omit to use profile or prior-job address. Pass structured fields only (address1, city, region, postalCode, etc.) — never formattedAddress."New value: +"Optional street-level address override. The profile or prior-job address is used otherwise. Accepted structured fields include address1, city, region, postalCode, etc.; formattedAddress is output only."
    • changedInput schema / properties / confirm_booking / description
      Previous value: -"false (default): return a rebooking preview; does NOT submit. true: submit the rebooking after the homeowner explicitly confirms."New value: +"false (default) returns a rebooking preview without submitting. true submits the rebooking."
    • changedInput schema / properties / context / description
      Previous value: -"Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names, phones, emails, street addresses, IDs, or other PII. Example: \"Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.\""New value: +"Optional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent."
    • changedInput schema / properties / job_description / description
      Previous value: -"Description of the new work; omit to reuse the prior job description"New value: +"Description of the new work; the prior job description is reused when absent"
    • changedInput schema / properties / job_id / description
      Previous value: -"Job ID from get_previous_jobs for the prior booking to rehire"New value: +"Identifier of the prior job"
    • changedInput schema / properties / location / description
      Previous value: -"Optional geocoding hint when address lacks coordinates. Omit in normal flows. When needed, pass exactly one of: lat+lng, zip, or text."New value: +"Optional geocoding hint when address lacks coordinates. Accepted forms are lat+lng, zip, or text."
    • changedInput schema / properties / name / description
      Previous value: -"Optional name override; omit to use authenticated homeowner profile"New value: +"Optional name override; the authenticated homeowner profile supplies the value otherwise"
    • changedInput schema / properties / phone / description
      Previous value: -"Optional phone override; omit to use authenticated homeowner profile"New value: +"Optional phone override; the authenticated homeowner profile supplies the value otherwise"
  2. Changed7 schema fields changed
    • addedInput schema / properties / context / anyOf
      Added value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / context / default
      Added value: +null
    • changedInput schema / properties / context / description
      Previous value: -"Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\""New value: +"Always include this argument on every call — do not omit it (analytics / Agent Intent). Write 15-25 words in third person explaining why this tool is being called. Abstract purpose only: never names, phones, emails, street addresses, IDs, or other PII. Example: \"Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.\""
    • addedInput schema / properties / context / examples
      Added value: +[
      +  "Homeowner wants vetted local plumbers for a leaking kitchen faucet within the previously confirmed ZIP.",
      +  "Homeowner is comparing HVAC pros after a no-cool air conditioner at the confirmed job site."
      +]
    • addedInput schema / properties / context / title
      Added value: +"Context"
    • removedInput schema / properties / context / type
      Removed value: -"string"
    • changedInput schema / required
      Previous value: -[
      -  "job_id",
      -  "context"
      -]New value: +[
      +  "job_id"
      +]
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already flag readOnlyHint=false and idempotentHint=false, but the description goes further by spelling out the consequence: repeated confirmed submissions create separate requests. It also discloses the auth failure mode ("auth_required") and the preview-versus-submit gate, which are not in the annotations.

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?

Every sentence carries a distinct fact — purpose, auth, preview gate, non-idempotency, return shape — with no redundancy, and the core action is stated first. Nothing could be cut without losing information an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter, open-world mutation tool, the description covers the pieces that matter: auth requirement and failure signal, preview-first workflow, non-idempotency risk, and override defaults. Return shape is already covered by an output schema, and the brief mention of returns is harmless.

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 description coverage is 89%, so the schema already documents job_id, the profile overrides, address/location forms and confirm_booking. The description's parameter sentence ("job ID and optional work, profile, location, and confirmation values") largely restates that mapping without adding format or precedence rules, so the baseline 3 applies.

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 states a specific verb and resource (creates a service request) and narrows the scope to a provider tied to a prior job ID, which is exactly what separates it from create_booking or the single-trade book_plumber/book_hvac siblings. An agent can identify the tool's unique job without reading the schema.

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?

It gives clear operating context: authentication is required, unauthenticated calls return "auth_required", and confirm_booking=false previews while true submits. It stops short of naming the alternative (create_booking) for the no-prior-job case or stating explicit when-not-to-use conditions, so the routing decision against siblings is left partly to inference.

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.