Skip to main content
Glama
Sign In

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

List Properties

list_properties
Read-onlyIdempotent

List all properties with IDs, short names, and full names.

location (optional): a Rent Manager Location ID, a comma-separated list, or "all" to run across every Location on this connection (see list_locations). Blank = all Locations if the connection has several, else its only Location. Output is labelled per Location; a Location that can't be reached is listed as skipped.

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
locationNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / location
      Added value: +{
+  "default": "",
+  "title": "Location",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so safety needs no restating, and the description instead adds real operational detail: results are labelled per Location and unreachable Locations are reported as skipped rather than failing the whole call. That partial-failure behavior is exactly the kind of trait annotations cannot convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then a scoped paragraph devoted entirely to the single parameter. No filler sentences; the density of the location paragraph is justified by the 0% schema coverage, though the backtick-heavy formatting is slightly noisy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need no prose, and the remaining unknowns for a one-parameter read tool — scope defaults, multi-Location behavior, partial failure — are all addressed. Nothing an agent needs to call this correctly is absent.

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

Parameters5/5

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

Schema coverage is 0%, so the description carries the full burden and does so completely: it names the identifier system (Rent Manager Location ID), the multi-value syntax (comma-separated), the wildcard ('all'), and the meaning of blank — all Locations when several exist, otherwise the single Location. Little is left to guess before invoking.

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?

States a specific verb and resource ('List all properties') and even enumerates the returned fields (IDs, short names, full names), which lets an agent distinguish this from sibling resolvers like list_locations, list_property_groups, or get_property_udfs without opening the schema.

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?

The location semantics make the calling context clear: a single ID, a comma-separated list, or 'all' for cross-Location runs, with 'see list_locations' as the explicit pointer for discovering IDs. What is missing is any statement of when to prefer this over property-scoped siblings, but the scoping guidance is concrete and actionable.

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

All AskRentAI toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources