Skip to main content
Glama
mcp-123bail
by lydstyl

get_properties_by_landlord

List all rental properties for a specified landlord, including lease counts, to quickly review portfolio holdings and occupancy data.

Instructions

List all properties (rental units) of a landlord, with lease counts

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": {
      "landlord": "<landlord>"
    },
    "name": "get_properties_by_landlord"
  }
}

Input Schema

NameRequiredDescriptionDefault
landlordYesLandlord name or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but "List" reasonably signals a read-only operation and "all properties" plus "with lease counts" adds some behavioral context. It does not disclose pagination, ordering, whether inactive properties are included, or what happens if the landlord has no properties.

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?

It is a single, front-loaded sentence with no wasted wording. The scope and included lease counts are stated immediately.

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 simple one-parameter read tool with no output schema, the description covers the core operation, scope, and the notable inclusion of lease counts. It leaves some minor details unspecified, such as what fields each property contains and whether lease counts are limited to active leases.

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?

Schema coverage is 100%, and the schema already explains that the landlord parameter accepts a name or ID. The description adds no additional parameter meaning beyond that baseline.

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 states a specific verb ("List") and resource ("properties (rental units)") scoped to a landlord, and it adds that lease counts are included. This distinguishes it from sibling tools such as get_tenants_by_landlord and get_payment_summary_by_landlord by resource.

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

Usage Guidelines2/5

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

The description does not explicitly say when to use this tool, when not to use it, or which sibling tool to choose for related landlord data. Usage is only implied by the phrase "of a landlord."

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