Skip to main content
Glama
mcp-123bail
by lydstyl

get_tenants_by_landlord

Lists all tenant emails and phone numbers linked to a landlord through their properties and leases.

Instructions

List all tenants (email, phone) linked to a landlord via their properties and leases

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_tenants_by_landlord"
  }
}

Input Schema

NameRequiredDescriptionDefault
landlordYesLandlord name or ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It does reveal the traversal path (properties and leases) and the returned fields, which implies a read-only listing, but it says nothing about pagination, empty results, permissions, or whether deactivated tenants are included.

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?

A single tight sentence with the resource front-loaded and the relationship scope following. Nothing is wasted, though the parenthetical field list is slightly awkward mid-sentence.

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 one-parameter read-only list tool with no output schema, the definition covers the anchor, the traversal logic, and the returned fields, which is close to sufficient. The main residual gap is disambiguation from the overlapping search_tenants sibling.

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 description coverage is 100% and there is only one parameter ('landlord'), so the schema already documents it as name or ID. The description adds mild framing by positioning the landlord as the anchor of the lookup, but no format or matching semantics beyond that.

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 ('List all tenants') and defines the relationship scope ('linked to a landlord via their properties and leases'), including the returned fields (email, phone). It does not differentiate itself from the sibling search_tenants, so an agent must infer the boundary.

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 tool is anchor-based on a landlord, which signals it is the right choice when a landlord is the starting point. There is no explicit when-to-use or when-not-to-use guidance, and no mention of search_tenants as the alternative path.

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