storedge-mcp

by sanjibani

Overview Schema Source Related Servers Discussions Admin

Python

Remote

list_available_units

List rentable units available for move-in at a facility. Check open inventory and unit sizes for immediate occupancy.

Instructions

List only units available for move-in.

Use when: "what 10x10 units do I have open?", "show rentable inventory".

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

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

B3.1/5.0

Behavior2/5

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

No annotations exist, so the description must disclose behaviors. It does not mention pagination, authentication, filtering logic beyond availability, or any side effects. This is insufficient.

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

Conciseness3/5

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

The description is very short and front-loaded, but it omits essential details for the sake of brevity. It could include more information without being verbose.

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?

With 3 parameters, no schema descriptions, and no annotations, the description should provide more context. It fails to explain pagination, facility filtering, or output structure, making it incomplete.

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?

Schema description coverage is 0%, so the description must explain parameters. It does not mention 'page', 'per_page', or 'facility_id' at all, leaving their meaning and usage to inference.

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 lists only units available for move-in, with a specific verb and resource. It distinguishes from siblings like 'list_units' by specifying the subset.

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?

It provides example queries ('what 10x10 units do I have open?', 'show rentable inventory') indicating when to use. However, it does not explicitly mention when not to use or contrast with alternatives like 'list_units'.

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