Skip to main content
Glama
Sign In
Podyx MCP

Podyx MCP

by Studio-Red-Barcelona
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

podyx_v1_get_studio

Read-onlyIdempotent

Retrieve the studio tied to the authenticated API key for read-only profile access; any tenant selectors supplied in the request are ignored.

Instructions

getStudio GET /api/v1/studio. 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_get_studio"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely useful behavior (the key resolves the studio; tenant selectors in the request are ignored), but it also carries irrelevant boilerplate about pagination defaults and quote reservation that cannot apply to a zero-parameter read, which muddies rather than clarifies behavior.

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 purpose is front-loaded in the first two sentences, which is good. However, the pagination sentence (page 1, 20 entries, cap 100, "follow all pagination") and the quote-reservation sentence are dead weight for a parameterless single-object read and read as copied API boilerplate.

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?

For a simple zero-parameter read this is close to adequate, but with no output schema the description never indicates what a studio record contains or its shape. The extraneous pagination and quote text also leaves the reader unsure whether this endpoint actually returns a list.

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

Parameters4/5

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

There are zero parameters, so the baseline is 4; the schema already forbids additional properties. The description's remark that tenant selectors are ignored is consistent with the empty schema and prevents an agent from trying to target a studio explicitly.

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 ("getStudio", "GET /api/v1/studio") and clarifies the resolution rule: the authenticated key determines which studio is returned. It does not name or contrast itself with any sibling, so an agent must infer why it would call this instead of podyx_v1_get_api_key or a list endpoint.

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?

"Read/preview only" and the note that tenant selectors are ignored imply when the tool is appropriate, but there is no explicit when-to-use or when-not-to-use guidance against alternatives. The closing sentence about quotes not reserving slots or locking prices is guidance for a different kind of operation and does not help select this tool.

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

Deploy Server

Other Tools