Skip to main content
Glama
mcp-123bail
by lydstyl

find_leases_by_tenant

Retrieve all leases for a tenant using their ID, full name, or email. Use this to identify rental agreements tied to a specific tenant in a self-hosted portfolio.

Instructions

Find all leases of a tenant by tenant ID, name, or email

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": {
      "tenant": "<tenant>"
    },
    "name": "find_leases_by_tenant"
  }
}

Input Schema

NameRequiredDescriptionDefault
tenantYesTenant ID, full name, or email

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?

No annotations are provided, so the description carries the entire behavioral burden. Beyond 'all leases' it discloses nothing about whether terminated or expired leases are included, how ambiguous name/email matches are resolved, what happens when no tenant matches, or whether results are paginated.

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?

A single front-loaded sentence with the resource and accepted key types, no filler. Nothing could be cut without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool with no output schema, the essentials are present, but the ambiguous 'all' scope and the absence of any result or empty-result behavior leave meaningful gaps for an agent deciding between this and get_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 description coverage is 100% and the parameter already documents 'Tenant ID, full name, or email'. The description merely restates that, adding no resolution-order or formatting guidance, so baseline 3 applies.

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 ('Find') and resource ('leases of a tenant'), and the lookup key. It is distinguishable from create_lease and get_active_leases at a high level, but the word 'all' is left ambiguous against get_active_leases' active-only scope, so the boundary is not fully drawn.

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: this is the tool to reach for when you have a tenant identifier and want their leases. However, there is no explicit when-not guidance, no mention of an alternative for active-only leases, and no prerequisites stated.

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