Podyx MCP

podyx_v1_list_rooms

Read-onlyIdempotent

Lists rooms for the authenticated studio with pagination and optional inactive rooms, providing read-only previews to review available spaces before booking.

Instructions

listRooms GET /api/v1/rooms. The authenticated key resolves the studio. Tenant selectors supplied in the request are ignored. Lists default to page 1 and 20 entries; page sizes are capped at 100. Read/preview only. Follow all pagination; a quote does not reserve a slot or lock a price.

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": "podyx_v1_list_rooms"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 7, 2026

TDQS

A3.5/5.0

Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds real behavior: tenant selectors are silently ignored, defaults are page 1 of 20, page size is capped at 100, and the caller is told to follow all pages. The closing sentence about a quote not reserving a slot or locking a price appears copied from a quoting tool and is irrelevant here, slightly muddying the signal.

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?

Front-loads the endpoint and the key scoping rule efficiently, but the final sentence about quotes and price locks does not earn its place in a room-listing tool. Removing it would make the definition noticeably tighter.

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?

No output schema exists, and the description says nothing about what a room record contains or what pagination metadata is returned, so the agent cannot judge return values. Scoping and paging behavior are well covered, but include_inactive and the response shape remain gaps.

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

Parameters3/5

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

Schema coverage is reported at 0%, so the description must compensate; it does explain the page/per_page defaults and the 1-100 clamp. However the third nested parameter, include_inactive, is never explained in either the schema or the description, so whether inactive rooms are returned by default is left ambiguous.

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?

States a specific verb and resource ('listRooms GET /api/v1/rooms') and adds the key scoping rule: the authenticated key resolves the studio and tenant selectors are ignored. It does not differentiate from the confusingly similar siblings podyx_list_room and podyx_get_room, which an agent would need to choose between.

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?

Usage is only implied: it is a read/preview listing of rooms for the authenticated studio, with an instruction to follow all pagination. There is no explicit when-to-use versus podyx_get_room (single room) or podyx_list_room, and no stated prerequisites beyond the API key.

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

Deploy Server