Skip to main content
Glama

pike13_guide

Guides you through Pike13 screens for managing client records, class rosters, enrollment, and reporting, and provides the sign-in link. Call this tool first when starting a Pike13 task.

Instructions

How to work in Pike13 (manage studio client records, class rosters, enrollment and reporting): 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": "pike13_guide"
  }
}

Input Schema

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

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 full behavioral burden. It discloses that this is a guide covering screens and the sign-in link, which implies informational/read-only use, but it does not clarify what the guide returns, whether it navigates anywhere, or how the optional task parameter affects the response.

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 description is a single compact sentence with the scope front-loaded in parentheses followed by a clear call-to-action. No sentence is wasted.

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 low-complexity guide tool with one optional parameter and no output schema, the description gives sufficient orientation: what it covers, what it includes, and that it should be called first. Minor gaps remain around return format and whether the guide is static or task-specific.

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 is already documented as 'What you want done in Pike13, in your words.' The description adds usage context through 'Call this first' but does not elaborate on how task input changes the guide output.

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 states a specific resource: guidance for working in Pike13, including screens, sign-in link, and covered workflows such as client records, rosters, enrollment, and reporting. It is clearly distinct from sibling action tools like click/open/read, though 'How to work in Pike13' is somewhat broad.

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?

The instruction 'Call this first' gives explicit ordering guidance and establishes this as the orientation step before using sibling action tools. It does not name when-not-to-use conditions or specific alternatives, but the primary usage context is clear.

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