storedge-mcp

by sanjibani

Overview Schema Source Related Servers Discussions Admin

Python

Remote

list_current_tenants

Retrieve a list of all currently active tenants with rented units, excluding moved-out tenants.

Instructions

List only currently-active tenants (not moved-out).

Use when: "show me everyone who has a unit rented right now".

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

Input Schema

Name	Required	Description	Default
`page`	No
`per_page`	No
`facility_id`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 8, 2026

TDQS

A3.8/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 full burden. It states the tool lists active tenants but does not disclose details like pagination behavior, default sorting, or whether facility_id is required. For a read-only list tool, this is adequate but not comprehensive.

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 extremely concise: two lines with no unnecessary words. The purpose is front-loaded and every word adds value. Perfect efficiency for a simple tool.

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?

The tool has three optional parameters and an output schema. The description is minimal, lacking guidance on filtering by facility_id or details about the return structure. While the output schema may cover return values, the description does not address use of the parameters, leaving some gaps for an AI agent.

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 parameters are entirely undocumented in the schema. The description does not explain any parameters (page, per_page, facility_id). Although parameter names are somewhat self-explanatory, the description fails to add meaning or usage guidance for the three parameters.

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 tool's purpose: 'List only currently-active tenants (not moved-out).' It uses a specific verb ('List') and resource ('currently-active tenants'), effectively distinguishing it from siblings like list_move_outs or list_tenants.

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?

Provides a concrete usage example: 'show me everyone who has a unit rented right now.' While it does not explicitly list when not to use or alternative tools, the context of siblings and the phrase 'only currently-active' implicitly guide appropriate use.

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