Skip to main content
Glama

create_gym_kiosk

Create a kiosk and get its one-time pairing code to enter on the kiosk screen. (confirm-gated: previews until confirm: true)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "organizationId": "<organizationId>",
      "name": "<name>"
    },
    "name": "create_gym_kiosk"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.
locationIdNo
organizationIdYesGym id (from list_my_organizations)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

The description discloses meaningful behavior beyond annotations: it is confirm-gated, previews until confirm: true, and returns a one-time pairing code for the kiosk screen. It does not mention required permissions or what happens if creation fails, but the preview/execute distinction is valuable for a mutation tool.

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?

Two short sentences with no wasted words. The main action and outcome are front-loaded, and the confirm-gating caveat is succinctly appended.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but the description explains the key return value: a one-time pairing code. The confirm preview/execute behavior is also covered. Missing detail about locationId and permissions keeps it from being fully complete.

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 only 50%, with name and locationId undocumented in both schema and description. The description restates the confirm gating but does not add meaning for name, organizationId, or locationId, so it fails to compensate for the coverage gap.

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 states a specific verb and resource: 'Create a kiosk', and adds the outcome 'get its one-time pairing code'. This clearly distinguishes it from sibling tools like list_gym_kiosks and revoke_gym_kiosk.

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?

The description implies when to use the tool by stating it creates a kiosk and issues a pairing code, and it explains confirm-gating. However, it gives no explicit when-not-use guidance or alternatives to list_gym_kiosks, revoke_gym_kiosk, or set_gym_kiosk_door.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.