Phorme Training

Teach my coach

teach_my_coach

Use this when a Phorme coach wants their AI coach to know something they teach: a cue, a drill, how they see a movement, a transcript of them explaining it. It adds it, in the coach's own words, to what their coach teaches from. Never invent or rewrite the coach's meaning. Set confirmation to true only after the coach said to add it.

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": {
      "brain_id": "<brain_id>",
      "title": "<title>",
      "text": "<text>",
      "confirmation": "<confirmation>"
    },
    "name": "teach_my_coach"
  }
}

Input Schema

Name	Required	Description
`text`	Yes	What the coach teaches, in their own words.
`title`	Yes	A short name for it, for example "How I cue the hinge".
`brain_id`	Yes	The brain id of the coach's own build, for example "cameron".
`confirmation`	Yes	True only after the coach said to add this.

Output Schema

Name	Required	Description	Default
`next`	No
`added`	Yes
`brain_id`	No
`passages`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 31, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare this is a non-destructive, non-readonly local write, so the description's job is to add context. It does: the content is persisted into the coach's teaching corpus, must preserve the coach's exact meaning ('Never invent or rewrite'), and requires an explicit confirmation gate. It does not describe reversibility or where the content is stored, which keeps it from a 5.

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?

Four tight sentences, front-loaded with the trigger and followed by the fidelity constraint and confirmation rule. Every sentence contributes a distinct operational instruction with no repetition.

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?

Output schema exists, so return values need no explanation, and the description covers the trigger, the fidelity requirement, and the confirmation gate for a mutation tool. Missing only minor context such as reversibility or error handling.

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%, so all four parameters are already documented in the input schema, including the confirmation const=true gate and the text/title purposes. The description reinforces the 'in the coach's own words' constraint and the confirmation timing, but adds little beyond what the schema already states, making the baseline 3 appropriate.

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 names a specific verb and resource: adding a coach's own teaching (cue, drill, movement view, transcript) to what their AI coach teaches from. The concrete examples make it distinguishable from nearby siblings like correct_my_coach and set_my_coach_principles, though it never names those alternatives explicitly.

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?

It opens with an explicit trigger ('Use this when a Phorme coach wants their AI coach to know something they teach') and adds a precondition for the confirmation flag. It stops short of stating when not to use it or naming which sibling to use instead.

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

All Phorme Training tools Inspect

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.