Skip to main content
Glama
Sign In

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

List Portfolios

list_portfolios
Read-onlyIdempotent

Show named portfolios + auto-detected dash-prefix portfolios.

``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. IDs (property, tenant, ...) belong
to one Location, so pass that Location when you filter by one.

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.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive behavior, and the description usefully adds that output is labelled per Location and unreachable Locations are reported as skipped. It also clarifies that IDs such as property and tenant IDs are scoped to one Location, which is important behavioral context beyond the annotations.

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?

The main purpose is front-loaded, and the remaining sentences provide useful parameter and behavior details. It is slightly verbose in formatting and could be tighter, but no sentence is clearly wasted.

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?

The output schema exists, so return values need not be explained in detail, and the description covers the only parameter plus skipped-location behavior. It is slightly incomplete in that it does not clarify what distinguishes a portfolio from a property group or explain when to choose this list tool over its siblings.

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?

Although the schema has 0% description coverage, the description fully compensates by defining location as a Rent Manager Location ID, a comma-separated list, or 'all', and by explaining the blank/default behavior and its relevance when filtering by Location-scoped IDs.

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 description states a clear verb and resource: it shows named portfolios plus auto-detected dash-prefix portfolios. It does not explicitly differentiate this tool from nearby listing tools such as list_property_groups or list_properties, so it falls short of 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?

The description explains how the optional location parameter behaves, including blank, 'all', and comma-separated values, and points to list_locations for Location IDs. However, it does not say when to use this tool instead of alternatives like list_property_groups, list_properties, or list_locations.

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