Skip to main content
Glama
smtchahal

nobrokerhood-mcp

by smtchahal

get_user_multiprofile_info

Fetch the authenticated user's profile, apartments, family members, society details, and pass codes from NoBrokerHood. Use to obtain apartment IDs and user data.

Instructions

Fetch the authenticated user's multiprofile information.

Use this when the user asks about their profile, apartments, family members, society details, or pass codes: "what apartments do I have?", "show my profile", "who are my family members?", "what's my pass code?", "which societies am I in?".

Also use this FIRST whenever another tool needs an apartment_id — unless the user explicitly provided the apartment_id, in which case use it directly. Call with fields=["data.apartments.apartment.id", "data.apartments.apartment.name", "data.apartments.apartment.displayName", "data.apartments.apartment.buildingName"] to identify the right apartment before proceeding. If exactly one apartment is returned, use its ID immediately without asking the user to confirm. If multiple apartments are returned, match the user's input against all of: name (full apartment name), displayName (short label), and buildingName (tower/block name) — the user may refer to any of these.

Args: fields: Dot-notation paths to include in the response. Always specify fields to avoid fetching the full profile (which includes family, notification settings, and other data rarely needed). Omit only if the user explicitly asks for their complete profile information. Examples: - ["data.apartments.apartment.id", "data.apartments.apartment.name", "data.apartments.apartment.displayName", "data.apartments.apartment.buildingName"] → compact apartment list for matching and obtaining an apartment_id - ["data.user.person.name", "data.user.person.phone"] → just the primary user's contact info - ["data.passCodes"] → just the pass codes map

Returns the raw API response dict containing:

  • user: primary user details (name, email, phone, photo)

  • family: list of family members registered under the account

  • apartments: all apartments the user has access to, each with apartment details, area/block info, society info, ownership type (OWNER/TENANT), and residency tag

  • passCodes: map of apartmentId → entry pass code

  • notifcationSettings: all notification toggle states

  • hasMultipleProfile: whether the user has profiles across multiple apartments

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fieldsNo
Behavior4/5

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

Discloses return structure (user, family, apartments, passCodes, notificationSettings, hasMultipleProfile) and explains that specifying fields avoids fetching full profile. No annotations provided, but description covers behavior well; could explicitly state read-only nature.

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?

Well-structured with clear sections: purpose, usage, args, returns. Slightly verbose due to repeated examples, but front-loaded and easy to parse.

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?

With one parameter, no output schema, and no annotations, the description provides comprehensive context: parameter usage, return structure, and guidance for common scenarios.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description thoroughly explains the 'fields' parameter: dot-notation paths, examples, default behavior, and advice to always specify fields to limit response. Adds crucial meaning beyond the raw schema.

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 clearly states 'Fetch the authenticated user's multiprofile information' and provides numerous specific use cases (e.g., 'what apartments do I have?', 'show my profile'). It distinguishes from sibling tools that handle visits.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit guidance on when to use: user queries about profile, apartments, family, society, pass codes. Also instructs to use first when another tool needs an apartment_id, with detailed steps for apartment matching.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/smtchahal/nobrokerhood-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server