Skip to main content
Glama
Sign In
OwnerRez MCP Server

OwnerRez MCP Server

by jgonzalez007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_quotes

Retrieve property quotes with optional property ID filtering to track and manage rental inquiries.

Instructions

List quotes, optionally filtered to comma-separated property IDs.

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

Input Schema

NameRequiredDescriptionDefault
max_itemsNo
property_idsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of explaining behavior. It communicates a read-only list operation and usefully specifies that property_ids is a comma-separated filter. However, it does not disclose behavior around max_items, pagination, ordering, invalid IDs, or result limits, leaving some behavioral aspects implicit.

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 sentence with the core verb and resource front-loaded, followed by the only important qualifier. It contains no filler, repetition, or unnecessary detail.

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 simple two-parameter listing tool with an output schema, the description covers the essential operation and the main filter detail. However, it omits any mention of max_items behavior and provides no usage guidance, which leaves the description adequate but not fully complete.

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?

Schema description coverage is 0%, so the description must compensate for both parameters. It adds meaning for property_ids by explaining the comma-separated filter format, but it says nothing about max_items, its effect, or its constraints. Partial coverage of parameters leaves a clear gap.

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 states a specific verb and resource: "List quotes." It also names the optional filtering dimension, and the resource name 'quotes' clearly distinguishes it from sibling listing tools like list_bookings, list_properties, and list_payments.

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 description implies its use case: retrieving quotes, optionally filtered by property IDs. However, it gives no explicit guidance about when to choose this tool over alternatives, nor does it mention any exclusions or conditions. The intended usage is understandable but not fully articulated.

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