Skip to main content
Glama

HireNimbus home services MCP

Book electrician

book_electrician
Read-onlyIdempotent

Searches HireNimbus providers for an electrician or electrical work, including jobs such as a dead outlet or outlet not working, breaker that keeps tripping, electrical panel upgrade, light fixture or ceiling fan installation, dimmer or switch replacement, EV charger installation, flickering lights, GFCI outlets, recessed lighting, hardwired smoke detectors, or exterior and landscape lighting. 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_electrician"
  }
}

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
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered and 'Read-only' in the description earns little. What the description genuinely adds is the no-authentication requirement and a hint at the return payload ('provider records and resolved location'), but it says nothing about pagination, result caps, or what happens when a ZIP has no providers.

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?

Purpose and the authentication note are front-loaded, which is good, but the middle is a 15-item enumeration of electrical jobs that is heavy for a single field-driven search. Roughly half the sentence could be trimmed while preserving matching value, and the structural ordering puts the least decision-relevant content in the middle.

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?

With an output schema present and rich annotations covering safety and openness, the description covers what the tool does, what it accepts, and roughly what it returns, plus the auth requirement. The remaining gap is pagination behavior and sibling disambiguation, which are meaningful but not fatal for a filtered-search tool.

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 carry only titles and defaults. The description merely enumerates 'a 5-digit US ZIP location, page, limit, and optional context' without adding format, bounds, or pagination semantics, so it does not compensate for the undocumented parameters.

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?

States a specific verb and resource: 'Searches HireNimbus providers for an electrician or electrical work', backed by a long list of concrete job types that make matching easy. However, it never addresses the naming tension with siblings find_electrician and create_booking — the tool is called 'book_electrician' but performs a search, and the description does not resolve which sibling an agent should prefer.

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?

There is no when-to-use / when-not-to-use guidance and no reference to any sibling, even though find_electrician and create_booking are obvious alternatives in the same family. The only usage-adjacent information is 'Does not require authentication' and the required ZIP input, which is context rather than routing guidance.

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.