Skip to main content
Glama

hapana_open

Opens a Hapana page in your signed-in Cloud Browser so you can manage studio clients, memberships, bookings, and payments; defaults to https://core.hapana.com.

Instructions

Open a Hapana page in your signed-in Cloud Browser (default https://core.hapana.com) to work with manage studio clients, memberships, bookings and payments.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://core.hapana.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two useful traits: the browser is already signed in (no auth step needed) and there is a default target URL. It does not say whether opening navigates the current tab or spawns a new one, what happens if a page is already open, or how failures surface — meaningful gaps for a navigation tool.

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?

One front-loaded sentence with no filler and the default URL placed inline where it is most useful. Minor deduction for the awkward phrase 'to work with manage studio clients', which is grammatically muddled and slightly obscures the intent.

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 one-optional-param tool with no output schema, the definition covers purpose, default target and signed-in state, which is close to sufficient. It still leaves out the behavioral details an agent needs (new tab vs. navigation, behavior when a page is already open), so it is adequate rather than complete.

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 coverage is 100% and the single optional parameter's default is already documented in the schema, so the description's restatement of the default URL adds no new meaning. Baseline 3 applies when the schema does the heavy lifting.

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+resource ('Open a Hapana page') and names the target surface ('your signed-in Cloud Browser'), which cleanly separates it from siblings like hapana_click, hapana_read and hapana_type that act on an already-open page. It stops short of explicitly contrasting itself with those siblings, so it is clear but not fully differentiated.

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 trailing clause ('to work with manage studio clients, memberships, bookings and payments') implies the context in which to use it, but there is no explicit when-to-use/when-not guidance and no mention of sequencing (e.g., open before click/read/type) or of hapana_close as the counterpart. Usage must be inferred.

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