Skip to main content
Glama

Binyan.im · בניינים

List apartments

list_apartments
Read-only

List apartments in a building. Contact details (email, phone) are left out unless includeContacts is true, and then only for callers who may manage that building.

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": {
      "buildingId": "<buildingId>"
    },
    "name": "list_apartments"
  }
}

Input Schema

NameRequiredDescriptionDefault
buildingIdYes
includeContactsNoInclude tenant and owner email and phone. Default false. Only callers who may manage the building get contacts; others get only their own.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds real behavioral value beyond that: contacts are excluded by default and, even when requested, are permission-gated per caller ("only for callers who may manage that building"), which an agent could not infer from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the core action front-loaded and the conditional detail following immediately. No filler, no restatement of the title, and every clause carries information.

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?

For a two-parameter read-only list tool with no output schema, the description covers the action, the default filtering behavior, and the permission rule on returned contacts. It stops short of describing ordering, pagination, or which apartment fields are returned, which would be useful for a list endpoint.

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

Parameters4/5

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

Schema coverage is 50%: includeContacts is documented in the schema, buildingId is not. The description reinforces the includeContacts default and adds the permission-scoping rule that the schema only hints at, and buildingId's meaning is clear from the tool's stated scope, so it largely compensates for the gap.

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?

The description opens with a specific verb and resource plus a scope constraint: "List apartments in a building." That distinguishes it from list_buildings well enough for selection, though it never names or contrasts a sibling explicitly.

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 implied by the required buildingId and by the conditional around includeContacts, giving the agent a sense of when the contact data appears. However, there is no explicit when-to-use/when-not-to-use guidance or routing to alternatives such as list_buildings or add_apartment.

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.

Resources