Skip to main content
Glama

ptminder_guide

Call this first to learn how to sign in to PTminder and use its screens for clients, sessions, workout plans, packages, payments, and reports.

Instructions

How to work in PTminder (clients, sessions, workout plans, packages, payments and reports): 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": "ptminder_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in PTminder, 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?

No annotations are supplied, so the description must carry the behavioral burden. It discloses the subject matter and that the result includes screens and a sign-in link, which implies an informational, non-mutating read, but it never states that explicitly nor describes the response shape or whether the guide becomes stale.

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 compact clauses with no filler, and the covered domains double as scannable routing cues. The most important directive, 'Call this first,' is placed last rather than front-loaded, which is a minor structural weakness.

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, single-optional-parameter guide tool with no output schema and no annotations, the description says what it contains and when to call it. Only the shape of the returned guidance and whether it needs refreshing are left implicit, which is a small gap at this complexity level.

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?

There is one optional parameter with 100% schema description coverage, so the schema already explains 'task' as the user's intent in their own words. The description adds no examples or constraints on how to phrase the task, so baseline 3 applies rather than higher.

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 PTminder – and enumerates the domains it covers (clients, sessions, workout plans, packages, payments, reports) plus its concrete content (screens, sign-in link). This clearly separates it from the action-oriented siblings like ptminder_click or ptminder_read, though it does not explicitly say 'I am the guidance tool, not the action tool.'

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' is explicit sequencing guidance that tells the agent to invoke this before the action siblings. It does not state any when-not condition or what to do on a second call, but for a one-shot orientation tool the trigger is unambiguous.

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