Skip to main content
Glama
mcp-123bail
by lydstyl

create_lease

Create a new lease for a property and one or more tenants, specifying start/end dates, monthly rent, charges, and payment due day.

Instructions

Create a new lease (bail) for a property and one or more tenants

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": {
      "propertyId": "<propertyId>",
      "tenantIds": "<tenantIds>",
      "startDate": "<startDate>",
      "rentAmount": "<rentAmount>",
      "chargesAmount": "<chargesAmount>",
      "paymentDueDay": "<paymentDueDay>"
    },
    "name": "create_lease"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional note
endDateNoEnd date YYYY-MM-DD (optional)
startDateYesStart date YYYY-MM-DD
tenantIdsYesTenant IDs (see search_tenants)
irlQuarterNoIRL quarter reference for rent indexation
propertyIdYesProperty ID
rentAmountYesMonthly rent in EUR (excluding charges)
chargesAmountYesMonthly charges in EUR (0 if none)
paymentDueDayYesPayment due day of month (1-28)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: no permission/auth requirements, no statement about overlapping or duplicate lease handling, no confirmation of what is returned (lease ID?), and no indication of whether the operation is reversible. Calling 'create' implies mutation, but side effects and failure modes are unstated.

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 compact sentence with no wasted words, front-loaded with the verb and resource. Its brevity is appropriate in form, though it leans toward under-specification rather than economy.

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

Completeness2/5

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

For a 9-parameter, 6-required mutation tool with no annotations and no output schema, the description does far too little: it doesn't say what the call returns, what preconditions must hold, or what errors to expect. The rich schema covers inputs, but the caller still lacks the operational context needed to invoke this safely.

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%, so every parameter including formats (YYYY-MM-DD), the paymentDueDay 1-28 range, and the pointer to search_tenants for tenantIds is documented in the schema itself. The description adds no meaning beyond that, so the 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 and resource ('Create a new lease (bail)') and names the scope: one property plus one or more tenants. It is clearly distinguishable from siblings like add_payment or find_leases_by_tenant, though it doesn't explicitly contrast with them.

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?

No when-to-use guidance, no prerequisites (e.g., property and tenants must already exist), and no mention of alternatives. An agent must infer from the parameter names alone that search_tenants/search_properties should be run first.

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