Skip to main content
Glama
Sign In
Buildium MCP Server

Buildium MCP Server

by luthersystems
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_lease

Retrieve detailed lease information using a lease ID. Returns a dictionary with lease details.

Instructions

Get a specific lease by ID.

Args: lease_id: The lease ID.

Returns: Lease details as dictionary.

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": {
      "lease_id": "<lease_id>"
    },
    "name": "get_lease"
  }
}

Input Schema

NameRequiredDescriptionDefault
lease_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior3/5

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

With no provided annotations, the description relies on the verb 'Get' to convey a read operation and adds that the return is a dictionary. It does not disclose error behavior for non-existent IDs or any access restrictions, but for a simple getter the core behavior is clear.

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?

The description is concise, front-loaded with the main sentence, and then uses 'Args' and 'Returns' sections. Every word earns its place with no filler.

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 get-by-ID tool, the description fully covers the main purpose and return format. It doesn't address edge cases like not-found behavior, but the presence of an output schema provides the expected lease structure, making this adequate.

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

Parameters2/5

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

The description only repeats the parameter name ('lease_id') and labels it as 'The lease ID,' which adds little meaning beyond the schema. Since the schema has no property descriptions and coverage is 0%, the description should provide more detail (e.g., type, constraints, purpose) but does not.

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 clearly states the action ('Get') on a specific resource ('a specific lease') using an identifier ('by ID'). This distinguishes it from list_leases (which retrieves all leases) and create/update_lease (which modify).

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?

The usage is implied by the 'get by ID' phrasing: use this when you have a known lease_id and need the full lease details. However, it does not explicitly mention when not to use it or point to list_leases for broader queries.

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

Deploy Server

Other Tools