Skip to main content
Glama

HireNimbus home services MCP

Book plumber

book_plumber
Read-onlyIdempotent

Searches HireNimbus providers for a plumber or plumbing repair, including jobs such as a leaky or dripping faucet, clogged drain or toilet, running toilet, low water pressure, water heater repair or replacement (including tankless), a leak under the sink, burst or frozen pipes, sump pump issues, garbage disposal repair, sewer line backup, shower valve replacement, or toilet installation. Does not require authentication. Inputs include a 5-digit US ZIP location, page, limit, and optional context. Returns provider records and resolved location. Read-only.

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": {
      "location": "<location>"
    },
    "name": "book_plumber"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
contextNoOptional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.
locationYes5-digit US ZIP code (e.g. "22307" or "94114").

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • 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 / location / description
      Previous value: -"Prefer a 5-digit US ZIP for location (e.g. \"22307\" or \"94114\"). This is the primary and preferred location input. After get_my_profile, if address.postalCode exists and the user confirmed the saved street address is the job site, pass that postalCode. Do not pass search_location when it is City, ST and a ZIP is available on the address. Never pass a street address, formattedAddress, or address1."New value: +"5-digit US ZIP code (e.g. \"22307\" or \"94114\")."
  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: -[
      -  "location",
      -  "context"
      -]New value: +[
      +  "location"
      +]
  3. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, and the description is consistent with them ("Read-only"). It then adds information the annotations do not carry: "Does not require authentication" and that the call returns provider records and resolved location. Remaining gaps – page size limits and pagination behavior – are minor given the annotation coverage.

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 core verb and resource are front-loaded, and the trailing sentences are short and purposeful. The long catalog of plumbing jobs is roughly 60 words of enumeration that help semantic matching but are heavier than necessary, diluting the otherwise tight structure.

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?

With an output schema present and annotations covering the safety profile, the description need not explain return values or reversibility. The critical omission is relational: among 20 siblings, including find_plumber and create_booking, the description never states whether this is a discovery step or a booking step, which is exactly what an agent needs to call it correctly.

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 50%: location and context are documented in the schema, while page and limit have only titles and defaults. The description restates the parameter list ("5-digit US ZIP location, page, limit, and optional context") without adding meaning – notably no bounds for limit or explanation of paging semantics – so it does not compensate for the undocumented half.

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 description gives a specific verb and resource ("Searches HireNimbus providers for a plumber") plus a long list of covered job types, so the search function is clear. However, it clashes with the tool name/title "book_plumber" and never distinguishes itself from the sibling find_plumber, so an agent must resolve a search-vs-booking ambiguity on its own.

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?

The enumerated repair scenarios imply when the tool is relevant, which is modestly useful context. But there is no explicit statement of when to choose this over find_plumber or how it relates to create_booking, and no exclusion guidance, so the routing decision is left 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.