Skip to main content
Glama
Sign In

Trainzilla Coach MCP

by io.github.Trainzilla
OverviewDiscussionsAdmin

update_session_client_notes

Set the notes the client sees on a session. (confirm-gated: previews until confirm: true)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "input": "<input>"
    },
    "name": "update_session_client_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
confirmNoMust be true to actually execute. If false/omitted, returns a preview only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With only readOnlyHint=false in annotations, the description does real work by disclosing the confirm-gate: it previews until confirm:true. This is meaningful behavioral context beyond the annotation. It stops short of a 5 because it doesn't state whether existing notes are overwritten or what the preview contains.

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?

Two short sentences, purpose front-loaded, with the gate condition immediately following. Nothing is wasted.

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?

Covers purpose and the confirm workflow for a nested mutation tool with no output schema. It leaves open the overwrite semantics of 'set' and the shape of the preview response, which matters for a notes mutation.

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 50% and the confirm parameter is already documented in the schema itself. The description adds value by clarifying that 'notes' are client-facing, but sessionId semantics and the replace-vs-append behavior of notes remain unstated.

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 ("Set the notes the client sees on a session") and adds the distinguishing qualifier that these are client-visible notes, separating it from internal note tools. It doesn't explicitly name a sibling it replaces, keeping it just short of a 5.

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 confirm-gated note implies a two-step preview/confirm workflow, giving some invocation context. However, there is no explicit when-to-use vs. when-not guidance or reference to alternatives like reschedule_session or cancel_session.

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

All Trainzilla Coach MCP toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources