Skip to main content
Glama
Sign In
Lanten MCP Server

Lanten MCP Server

by lanten-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_tenants

Search and paginate through tenants by name, email, phone, or unit address. Returns a paginated list matching your query.

Instructions

List tenants for the account. Supports free-text search across name, email, phone, and unit address. Returns paginated results.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_tenants"
  }
}

Input Schema

NameRequiredDescriptionDefault
searchNoSearch across name, email, phone, unit address
pageNoPage number (default 1)
pageSizeNoResults per page (max 50, default 20)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. Mentions pagination and free-text search fields but lacks details on sorting, search behavior (e.g., partial match, case sensitivity), or output format. Adequate but not detailed.

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?

Two concise sentences, front-loaded with purpose. No unnecessary words.

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 list tool with three optional parameters and no output schema, the description covers listing, search, and pagination. Missing details on output structure (e.g., array of tenants) but not critical. Mostly complete.

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%, so baseline is 3. Description adds minimal extra meaning: it repeats search fields already in schema and states 'Returns paginated results' which relates to page/pageSize. No significant new information.

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?

Clearly states 'List tenants for the account' with specific resource and action. Distinguishes from sibling tools like get_tenant (single tenant) and list_units/list_work_orders (different entities).

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

Usage Guidelines4/5

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

Indicates support for free-text search across specific fields, providing context on when to use the search parameter. No explicit exclusions or alternatives mentioned, but the context is clear.

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