Msty Admin MCP

List turnstiles

list_turnstiles

Read-onlyIdempotent

Retrieve Turnstile and Turnstiles vNext routing definitions from Studio as read-only JSON, up to a configurable limit, to inspect routing setup.

Instructions

List Turnstile and Turnstiles vNext routing definitions from Studio. Use get_studio_entity with entity=turnstiles for one row, and list_studio_catalogue for counts. Read-only. Returns JSON items up to limit.

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum rows. Integer from 1 to 500. Default 100.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv6.2.1Nov 1, 2026
- addedInput schema / properties / limit / description
```
Added value: +"Maximum rows. Integer from 1 to 500. Default 100."
```
Addedv6.1.5Oct 16, 2026

TDQS

A4.5/5.0

Behavior4/5

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

While annotations handle the read-only status, the description adds crucial behavioral context by specifying the source ('from Studio') and the expected return structure ('JSON items up to limit'). This adds value beyond the formal structured data.

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 definition is extremely concise, front-loading all essential information and cross-reference instructions within two efficient sentences. There is no unnecessary fluff.

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?

Given the low complexity (one parameter) and rich sibling context, the description provides a highly complete picture of what the tool does and how it fits into the larger ecosystem of routing definition management.

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?

With 100% schema description coverage, the description fulfills the baseline requirement. It reiterates the 'limit' function in terms of result bounding, but adds no significant semantic meaning beyond the schema's formal definition.

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 resource being listed (Turnstile and Turnstiles vNext routing definitions) and immediately distinguishes its purpose from related tools by specifying when to use get_studio_entity versus list_studio_catalogue.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides excellent usage guidelines by specifying exactly when to employ related siblings: get_studio_entity for single-row lookups and list_studio_catalogue for aggregated counts.

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

Deploy Server