Skip to main content
Glama
Sign In
OwnerRez MCP Server

OwnerRez MCP Server

by jgonzalez007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_properties

Retrieve property listings with IDs, names, addresses, and timezones to manage rental data through natural language queries.

Instructions

List properties (id, name, address, timezone).

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_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_itemsNo
active_onlyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior2/5

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

There is no information about side effects (though likely read-only), ordering, pagination, or default behavior. The schema parameters (max_items, active_only) are not explained, so the tool's runtime behavior remains opaque.

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 a single, concise sentence that conveys the essential purpose without extraneous detail. It is well-structured and easy to parse.

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?

The description omits explanations of parameters and does not include an output schema, leaving the return format and filtering semantics unknown. This makes the tool incomplete for an agent to use effectively.

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

Parameters1/5

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

The description does not explain the meaning or usage of the input parameters. Without context, an agent cannot know what 'max_items' or 'active_only' control, nor how they affect the results.

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 (list) and the resource (properties), with a parenthetical indicating the fields returned. It is unambiguous and distinguishes this tool from siblings like list_bookings or list_owners.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention scenarios like filtering by active status or limiting results, nor does it contrast with other list tools.

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