Skip to main content
Glama
smtchahal

nobrokerhood-mcp

by smtchahal

list_visits

List current, expired, and denied gate visits for an apartment, providing visitor details, timings, and approval status.

Instructions

List current, past (expired), and denied visits for an apartment.

Use this when the user asks about gate activity (current, historical, or denied): "who's at the gate?", "who came today?", "show past visitors", "any denied entries?", "who visited recently?", "what deliveries came in?", "what deliveries are coming today?". Do NOT use for pending pre-approvals that haven't arrived — use list_expected for that.

Returns all categories in one call. Each category is a separate list:

  • data.current: visitors presently at the gate (checked in, not yet out)

  • data.expired: completed past visits (checked in and checked out)

  • data.denied: entry attempts that were denied at the gate

  • data.pending: pre-approved visits not yet arrived (overlaps with list_expected)

Each visit entry includes: company, visitor name/phone, inTime, outTime, gate name, approvedBy, approvalType, visitorType, and approval status. Company is at the top-level company field and also at visitorProfile.company.

Call get_user_multiprofile_info first to obtain the apartment_id if not already known. Skip if the user explicitly provided it.

Args: apartment_id: The apartment ID to list visits for. Fetch from get_user_multiprofile_info → data.apartments.apartment.id. page: Page number, 1-indexed. Default 1. Applies to all lists. page_size: Number of results per page. Default 10. fields: Dot-notation paths to filter the response. Strongly recommended — omitting returns all four categories with full visitor data, which is large. Use fields to fetch only what the query needs: ["data.current"] → who's at the gate right now ["data.expired"] → today's completed visits ["data.current", "data.expired"] → active + past visits ["data.expired.company", "data.expired.inTime"] → company + entry time ["data.currentTotal", "data.expiredTotal", "data.deniedTotal"] → counts only Omit only if the user explicitly wants everything.

Returns the raw API response dict.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNo
fieldsNo
page_sizeNo
apartment_idYes
Behavior4/5

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

No annotations provided, so description carries full burden. It details return categories, pagination behavior, and field usage. Does not explicitly state idempotency or safety, but as a list operation it is clearly non-destructive.

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 sections, but slightly verbose given the complexity. However, every sentence adds value and no redundancy. Minor trim potential.

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?

No output schema, but description fully explains return categories and content. Also addresses prerequisite (apartment_id retrieval). No missing information for a list tool with no output schema.

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 adds extensive meaning: explains apartment_id source, page/page_size defaults, and fields parameter with concrete examples and recommendations. This far exceeds schema information.

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 the tool lists current, past, and denied visits for an apartment. It distinguishes from the sibling tool list_expected by explicitly stating what not to use it for.

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?

Provides explicit when-to-use examples (e.g., 'who's at the gate?') and when-not-to-use (pending pre-approvals, use list_expected). Also instructs to call get_user_multiprofile_info first to obtain apartment_id.

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