Skip to main content
Glama

HireNimbus home services MCP

Get my profile

get_my_profile
Read-onlyIdempotent

Returns the authenticated homeowner profile as structured JSON. Fields include status, name, phone, address, search_location, error_code, and message. Status values are "ok", "error", and "auth_required". search_location is a 5-digit ZIP from address.postalCode (e.g. "22307" or "94114").

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_my_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
contextNoOptional analytics context for a brief, non-identifying summary of the request purpose. The value is recorded as Agent Intent.

Output Schema

NameRequiredDescriptionDefault
nameNoHomeowner full name from profile (present when status is ok)
phoneNoHomeowner phone from profile (present when status is ok)
statusYesOutcome: "ok" when profile loaded, "auth_required" when unsigned-in, "error" otherwise
addressNoFull service street address on file with fields address1, address2, city, region, postalCode, country, formattedAddress
messageNoError or auth_required explanation
error_codeNoStable code such as "AUTH_REQUIRED" when status is auth_required
search_locationNo5-digit US ZIP from address.postalCode (e.g. "22307" or "94114").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 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."
    • changedOutput schema / $defs / HomeownerAddress / properties / formattedAddress / description
      Previous value: -"Single-line formatted address when available (read-only; do not pass on input)"New value: +"Single-line formatted address when available (output only)"
    • changedOutput schema / examples
      Previous value: -[
      -  {
      -    "address": {
      -      "address1": "123 Main St",
      -      "address2": null,
      -      "city": "Alexandria",
      -      "country": "US",
      -      "formattedAddress": "123 Main St, Alexandria, VA 22314",
      -      "postalCode": "22314",
      -      "region": "VA"
      -    },
      -    "message": null,
      -    "name": "Jane Doe",
      -    "phone": "+15551234567",
      -    "search_location": "22314",
      -    "status": "ok"
      -  },
      -  {
      -    "address": null,
      -    "message": "No authenticated homeowner profile found.",
      -    "name": null,
      -    "phone": null,
      -    "search_location": null,
      -    "status": "error"
      -  },
      -  {
      -    "address": null,
      -    "error_code": "AUTH_REQUIRED",
      -    "message": "No HireNimbus account is connected. Searching and browsing pros works without an account.",
      -    "name": null,
      -    "next_action": "continue_discovery",
      -    "phone": null,
      -    "search_location": null,
      -    "status": "auth_required"
      -  }
      -]New value: +[
      +  {
      +    "address": {
      +      "address1": "123 Main St",
      +      "address2": null,
      +      "city": "Alexandria",
      +      "country": "US",
      +      "formattedAddress": "123 Main St, Alexandria, VA 22314",
      +      "postalCode": "22314",
      +      "region": "VA"
      +    },
      +    "message": null,
      +    "name": "Jane Doe",
      +    "phone": "+15551234567",
      +    "search_location": "22314",
      +    "status": "ok"
      +  },
      +  {
      +    "address": null,
      +    "message": "No authenticated homeowner profile found.",
      +    "name": null,
      +    "phone": null,
      +    "search_location": null,
      +    "status": "error"
      +  },
      +  {
      +    "address": null,
      +    "error_code": "AUTH_REQUIRED",
      +    "message": "Authentication is required for this request.",
      +    "name": null,
      +    "phone": null,
      +    "search_location": null,
      +    "status": "auth_required"
      +  }
      +]
    • removedOutput schema / properties / next_action
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "enum": [
      -        "continue_discovery",
      -        "connect_to_book"
      -      ],
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "description": "When status is auth_required: \"continue_discovery\" means search and show pros without OTP; \"connect_to_book\" means start phone/OTP connect now",
      -  "title": "Next Action"
      -}
    • changedOutput schema / properties / search_location / description
      Previous value: -"5-digit US ZIP from address.postalCode (e.g. \"22307\" or \"94114\") — pass to search_providers.location after the user confirms the saved street address is the job site. Never City, ST, a street line, formattedAddress, or address1."New value: +"5-digit US ZIP from address.postalCode (e.g. \"22307\" or \"94114\")."
  2. Changed6 schema fields changed
    • changedOutput schema / examples
      Previous value: -[
      -  {
      -    "address": {
      -      "address1": "123 Main St",
      -      "address2": null,
      -      "city": "Alexandria",
      -      "country": "US",
      -      "formattedAddress": "123 Main St, Alexandria, VA 22314",
      -      "postalCode": "22314",
      -      "region": "VA"
      -    },
      -    "message": null,
      -    "name": "Jane Doe",
      -    "phone": "+15551234567",
      -    "search_location": "22314",
      -    "status": "ok"
      -  },
      -  {
      -    "address": null,
      -    "message": "No authenticated homeowner profile found.",
      -    "name": null,
      -    "phone": null,
      -    "search_location": null,
      -    "status": "error"
      -  }
      -]New value: +[
      +  {
      +    "address": {
      +      "address1": "123 Main St",
      +      "address2": null,
      +      "city": "Alexandria",
      +      "country": "US",
      +      "formattedAddress": "123 Main St, Alexandria, VA 22314",
      +      "postalCode": "22314",
      +      "region": "VA"
      +    },
      +    "message": null,
      +    "name": "Jane Doe",
      +    "phone": "+15551234567",
      +    "search_location": "22314",
      +    "status": "ok"
      +  },
      +  {
      +    "address": null,
      +    "message": "No authenticated homeowner profile found.",
      +    "name": null,
      +    "phone": null,
      +    "search_location": null,
      +    "status": "error"
      +  },
      +  {
      +    "address": null,
      +    "error_code": "AUTH_REQUIRED",
      +    "message": "No HireNimbus account is connected. Searching and browsing pros works without an account.",
      +    "name": null,
      +    "next_action": "continue_discovery",
      +    "phone": null,
      +    "search_location": null,
      +    "status": "auth_required"
      +  }
      +]
    • addedOutput schema / properties / error_code
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "Stable code such as \"AUTH_REQUIRED\" when status is auth_required",
      +  "title": "Error Code"
      +}
    • changedOutput schema / properties / message / description
      Previous value: -"Error explanation when status is error"New value: +"Error or auth_required explanation"
    • addedOutput schema / properties / next_action
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "continue_discovery",
      +        "connect_to_book"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "description": "When status is auth_required: \"continue_discovery\" means search and show pros without OTP; \"connect_to_book\" means start phone/OTP connect now",
      +  "title": "Next Action"
      +}
    • changedOutput schema / properties / status / description
      Previous value: -"Outcome: \"ok\" when profile loaded, \"error\" otherwise"New value: +"Outcome: \"ok\" when profile loaded, \"auth_required\" when unsigned-in, \"error\" otherwise"
    • changedOutput schema / properties / status / enum
      Previous value: -[
      -  "ok",
      -  "error"
      -]New value: +[
      +  "ok",
      +  "error",
      +  "auth_required"
      +]
  3. Changed3 schema fields changed
    • 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."
      +]
    • changedInput schema / required
      Previous value: -[
      -  "context"
      -]New value: +[]
  4. First observed

TDQS

A3.7/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 closed-world, so the safety bar is low. The description adds genuinely new behavioral detail: the three status values including "auth_required" (an auth-failure mode the agent must handle) and the presence of error_code/message, which is context annotations do not provide.

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 purpose and then the field inventory. Each sentence carries information, though the field list and the search_location example are slightly more granular than needed given an output schema exists.

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, the description needn't document return shapes, yet it adds useful field and status semantics. It is nearly complete for a zero-required-param read, with the only real gap being how the profile (especially search_location and auth_required) should drive subsequent sibling calls.

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?

There is one optional parameter (context), and schema description coverage is 100% with its own description and examples, so the schema does the work. The description adds nothing about the context parameter, which matches the baseline 3 for fully documented schemas.

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: returns the authenticated homeowner profile as structured JSON, and enumerates the fields returned. No sibling tool overlaps with this resource, so an agent can distinguish it easily, though the description never explicitly says what it is not for (e.g. provider lookups belong to get_provider_details).

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?

Usage is only implied: the mention of search_location as a 5-digit ZIP from address.postalCode hints that this is how an agent obtains the confirmed ZIP before searching, but the description never says when to call it, whether it must precede search_providers, or how to react to status "auth_required".

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.