Skip to main content
Glama

HireNimbus home services MCP

Search providers

search_providers
Read-onlyIdempotent

Searches providers by home service keyword and location. Does not require authentication. Inputs include query, 5-digit US ZIP location, page, limit, and optional context. Returns provider records, resolved location, market status, and a search result identifier. 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": {
      "query": "<query>",
      "location": "<location>"
    },
    "name": "search_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
limitNo
queryYesService keyword for a home service category (e.g. cleaning, landscaping, roofing).
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. Changed3 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\")."
    • changedInput schema / properties / query / description
      Previous value: -"Service keyword for non-top categories (e.g. cleaning, landscaping, roofing). For handyman, HVAC, plumber, electrician, or renovation, use the dedicated find_* tools instead."New value: +"Service keyword for a home service category (e.g. cleaning, landscaping, roofing)."
  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: -[
      -  "query",
      -  "location",
      -  "context"
      -]New value: +[
      +  "query",
      +  "location"
      +]
  3. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description still adds real value by disclosing the no-authentication requirement and summarizing what comes back (provider records, resolved location, market status, search result identifier), which is not derivable from the annotations. It does say 'Read-only', which merely restates readOnlyHint, and says nothing about rate limits or result-set bounds.

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?

Four short sentences, front-loaded with the core action followed by access, inputs, and returns in a logical scan order. The trailing 'Read-only.' is pure redundancy against the annotations and could be dropped.

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?

Inputs are fully named and an output schema exists, so no return-value explanation is required, and the auth note removes a common blocker. What is missing for a tool in this crowded sibling set is positional clarity: nothing tells the agent how this relates to find_plumber/find_electrician or that its output's 'search result identifier' feeds downstream booking tools.

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?

All five parameters are enumerated (query, ZIP location, page, limit, optional context), which maps cleanly to the schema. But the detail offered -- '5-digit US ZIP', 'optional context' -- largely duplicates the property descriptions, and at 60% schema coverage the less obvious page/limit semantics still get no elaboration on defaults or cap behavior.

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 providers') plus the two dimensions the search keys on ('home service keyword and location'), so the agent knows what the tool does. It does not name or distinguish itself from the many category-specific find_* siblings, so differentiation is only implied.

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?

Provides one useful usage fact -- 'Does not require authentication' -- which tells the agent it can call this pre-auth. Beyond that there is no when-to-use or when-not-to-use guidance, and given siblings like find_plumber, find_hvac, and find_handyman, an agent must infer whether this generic keyword search replaces or complements them.

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.