Skip to main content
Glama

fitune_open

Open a Fitune admin page in your signed-in Cloud Browser to manage studio classes, bookings, memberships, invoices, and payroll.

Instructions

Open a Fitune page in your signed-in Cloud Browser (default https://admin.fitune.io) to work with studio classes, bookings, memberships, invoices and payroll.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://admin.fitune.io

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that the page opens in the user's signed-in Cloud Browser and names a default URL, but it does not explain navigation side effects, whether an existing page is replaced, or what the tool returns.

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 a single front-loaded sentence with no filler. It delivers purpose, environment, default, and domain use cases efficiently.

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?

For a simple one-parameter navigation tool with full schema coverage and no output schema, the description is largely complete. It covers purpose, default URL, and signed-in browser context, though it could clarify workflow relationships with sibling browser tools.

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 description coverage is 100%, and the single url parameter is documented in the schema with its default. The description adds context about the Fitune admin domain but does not add URL syntax, constraints, or other meaning beyond the schema.

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: open a Fitune page in the signed-in Cloud Browser. It also names the default URL and the Fitune domain scope, making it clearly distinguishable from browser-interaction siblings like click, read, or close.

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 this is used to reach the Fitune admin surface for classes, bookings, memberships, invoices, and payroll. It does not explicitly say when to use this versus fitune_read or how it fits into a browser workflow, so usage guidance remains implicit rather than explicit.

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