Skip to main content
Glama

pike13_open

Opens a Pike13 page in your signed-in Cloud Browser to manage client records, class rosters, enrollment, and reporting. Use it to start studio workflows with your existing session.

Instructions

Open a Pike13 page in your signed-in Cloud Browser (default https://pike13.com) to work with manage studio client records, class rosters, enrollment and reporting.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://pike13.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; it does usefully disclose that the browser is a signed-in session, so authentication state is carried over, and it names the default target. It says nothing about what happens on failure, redirects, or whether the opened page is left in a changed navigation state, and there is no output schema to cover return values.

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?

A single front-loaded sentence with no filler, giving the action and the target environment immediately. It is mildly overstuffed by the enumerated use cases, but nothing is wasted or buried.

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?

Proportionate for a simple no-output, single-parameter navigation tool, and the signed-in-session note is the key context an agent needs. It still leaves the follow-up expectation unstated, i.e. that content must then be read via pike13_read rather than assumed from this call alone.

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?

Only one optional 'url' parameter and the schema already documents it at 100% coverage including the default. The description merely restates the same default, adding no format rules, relative-vs-absolute guidance, or deep-link constraints.

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 ("Open a Pike13 page") plus where it happens ("in your signed-in Cloud Browser"), which is enough to tell it apart from pike13_click, pike13_read and pike13_type. The trailing purpose clause (client records, rosters, enrollment, reporting) is broad and slightly garbled but does add scope. No explicit contrast with sibling tools.

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?

Usage is only implied: the agent must infer that this is the navigation entry point that precedes pike13_read or pike13_click. There is no statement of when to use this instead of pike13_status or another navigation route, and no prerequisites or sequencing spelled out.

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