Skip to main content
Glama

hapana_guide

Call this first to learn how to work in Hapana: find screens, the sign-in link, and steps for managing studio clients, memberships, bookings, and payments.

Instructions

How to work in Hapana (manage studio clients, memberships, bookings and payments): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Hapana, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description must carry behavioral disclosure itself. It implies a read-only informational resource and pre-empts the main behavioral question by saying to call it first, but it never states that it causes no side effects, whether results are cached or static, or what form the guidance arrives in.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, no filler, with the domain scope and the 'call this first' directive both up front. The colon-and-parenthetical construction is slightly clunky but the compact domain list earns its space by telling the agent what topics the guide covers.

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 one-parameter, annotation-free orientation tool this covers the essentials of what it is and when to call it. It leaves the return shape unspecified (prose guide, screen list, link only), which matters here because there is no output schema to fall back on.

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?

The single 'task' parameter is fully documented in the schema ('What you want done in Hapana, in your words'), so the schema already does the work and 100% coverage sets the baseline at 3. The description adds nothing about how the free-text task phrasing shapes the returned guidance, which is the one place extra meaning would have helped.

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?

The description names the resource ('Hapana') and enumerates the domain it covers: studio clients, memberships, bookings, payments, plus screens and the sign-in link. That is enough to separate it from the action-oriented siblings (hapana_click, hapana_type, hapana_open), though the framing 'How to work in Hapana' is more of a topic label than a crisp verb+resource statement.

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

Usage Guidelines4/5

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

'Call this first' gives explicit sequencing guidance that no sibling name implies, which is exactly the routing information an agent needs at session start. It stops short of stating when this tool is unnecessary (e.g. once orientation is done) or how it relates to hapana_status, so it is clear context without exclusions.

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