Skip to main content
Glama
mcp-123bail
by lydstyl

search_tenants

Search tenants by name, first name, or email to locate rental records and support lease, payment, or tenant management tasks.

Instructions

Search tenants by name, first 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": {
      "query": "<query>"
    },
    "name": "search_tenants"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSearch string (name, firstName, 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?

With no annotations, the description carries the full disclosure burden and supplies very little: it does not state that the operation is read-only, whether matching is exact/prefix/fuzzy or case-insensitive, how many results come back, or whether pagination exists. Only the set of searchable fields is conveyed, which is already apparent from the parameter name.

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?

One short clause, zero filler, and the core action is front-loaded. Nothing could be removed 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, no-output-schema tool this is minimally viable: the action is unambiguous, but matching behavior and result-set expectations are left entirely unspecified, which matters for a search tool where an agent must interpret hits and misses.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines the query string and its accepted fields. The description merely restates those same fields, adding no syntax, formatting, or matching-semantics detail beyond structured data.

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?

The fragment states a specific verb and resource ("Search tenants") and enumerates the searchable fields (name, first name, email), so an agent knows exactly what the tool retrieves. It does not distinguish itself from sibling lookups such as get_tenants_by_landlord, which is the only missing element for a 5.

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?

Use is only implied: an agent can infer it should call this when it holds a name or email fragment, but the description never says when to prefer this over the sibling list/lookup tools or what to do if no fragment is known. No exclusions or prerequisites are given.

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