goldseam

Open Coach

open_coach

Open a visible, speaking coach (coach, advisor, counselor, teacher, mentor or another role) in this chat as an MCP App view, for any GoldSeam service. Give the role and your service's own context in any shape; send a coach object from an earlier open_coach to reopen the same coach without resetting anything. The view asks the host for fullscreen when the host offers it and shows the mode it actually granted, the coach sized to the space the host gives, and what the host supports, including whether spoken replies can reach this chat. Every opening starts a coach session (session_minutes, 30 when omitted): the view turns the person's Talk switch on by itself, and you listen with coach_listen through this same turn until the session's time is up or they say they are done. You conduct the conversation: speak through the coach with coach_say. GoldSeam keeps nothing; keep the coach object.

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

Input Schema

Name	Required	Description
`role`	No	The coach's role, e.g. coach, advisor, counselor, teacher, mentor
`actor`	No	Optional: the coach's name; the role when omitted
`coach`	No	The coaching context an earlier open_coach returned (its coach object). Send it to reopen the same coach: same conversation, same size preset and display mode, nothing reset.
`context`	No	The calling service's own context for the coach (what is being worked on, where it stands), kept with the coaching context. Sent, it replaces the earlier context; omitted when reopening with coach, the coach keeps the context it had
`size_preset`	No	fit: as large as the space allows; natural: the poses' own size, never larger than the space
`display_mode`	No	The mode the view asks the host for; fullscreen when omitted. The host decides; the view shows what it granted.
`session_minutes`	No	How long the coach session lasts, in minutes, when the person names a length; 30 when omitted

Output Schema

Name	Required	Description
`view`	No
`coach`	No	The coaching context: coach_id (GoldAvatar's conversation), actor, role, seat, page_url, feed_after (where the coach view starts reading GoldAvatar's feed), picture (the poses the coach view draws the coach from, with their proportions and where their files are, from GoldAvatar's pose manifest), voice (GoldAvatar's voice service), size_preset, display_mode, the caller's context, session (the coach session this opening started: minutes, started_at, ends_at, which coach_listen takes as session_ends_at, quiet_after_seconds and quiet_from, the coach view's silence watcher), script (the senders and note kinds the coach view's script player writes with), and replaced (previous_coach_id, why) when status is replaced: the earlier coaching context was closed or unknown to GoldAvatar Messaging, so a new one was opened
`limits`	No
`status`	No
`problem`	No
`replies`	No
`contract`	Yes
`statement`	Yes
`how_to_speak`	No
`next_actions`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

changedOutput schema / properties / coach / description

Previous value: -"The coaching context: coach_id (GoldAvatar's conversation), actor, role, seat, page_url, feed_after (where the coach view starts reading GoldAvatar's feed), picture (the poses the coach view draws the coach from, with their proportions and where their files are, from GoldAvatar's pose manifest), voice (GoldAvatar's voice service), size_preset, display_mode, the caller's context, session (the coach session this opening started: minutes, started_at, ends_at, which coach_listen takes as session_ends_at, quiet_after_seconds and quiet_from, the coach view's silence watcher), and replaced (previous_coach_id, why) when status is replaced: the earlier coaching context was closed or unknown to GoldAvatar Messaging, so a new one was opened"New value: +"The coaching context: coach_id (GoldAvatar's conversation), actor, role, seat, page_url, feed_after (where the coach view starts reading GoldAvatar's feed), picture (the poses the coach view draws the coach from, with their proportions and where their files are, from GoldAvatar's pose manifest), voice (GoldAvatar's voice service), size_preset, display_mode, the caller's context, session (the coach session this opening started: minutes, started_at, ends_at, which coach_listen takes as session_ends_at, quiet_after_seconds and quiet_from, the coach view's silence watcher), script (the senders and note kinds the coach view's script player writes with), and replaced (previous_coach_id, why) when status is replaced: the earlier coaching context was closed or unknown to GoldAvatar Messaging, so a new one was opened"

Changed2 schema fields changedNov 5, 2026

addedInput schema / properties / session_minutes

Added value: +{
+  "description": "How long the coach session lasts, in minutes, when the person names a length; 30 when omitted",
+  "minimum": 1,
+  "type": "integer"
+}

changedOutput schema / properties / coach / description

Previous value: -"The coaching context: coach_id (GoldAvatar's conversation), actor, role, seat, page_url, feed_after (where the coach view starts reading GoldAvatar's feed), picture (the poses the coach view draws the coach from, with their proportions and where their files are, from GoldAvatar's pose manifest), voice (GoldAvatar's voice service), size_preset, display_mode, the caller's context, and replaced (previous_coach_id, why) when status is replaced: the earlier coaching context was closed or unknown to GoldAvatar Messaging, so a new one was opened"New value: +"The coaching context: coach_id (GoldAvatar's conversation), actor, role, seat, page_url, feed_after (where the coach view starts reading GoldAvatar's feed), picture (the poses the coach view draws the coach from, with their proportions and where their files are, from GoldAvatar's pose manifest), voice (GoldAvatar's voice service), size_preset, display_mode, the caller's context, session (the coach session this opening started: minutes, started_at, ends_at, which coach_listen takes as session_ends_at, quiet_after_seconds and quiet_from, the coach view's silence watcher), and replaced (previous_coach_id, why) when status is replaced: the earlier coaching context was closed or unknown to GoldAvatar Messaging, so a new one was opened"

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / display_mode / description

Previous value: -"The mode the view asks the host for; pip (floating) when omitted. The host decides; the view shows what it granted."New value: +"The mode the view asks the host for; fullscreen when omitted. The host decides; the view shows what it granted."

Changed1 schema field changedNov 3, 2026

changedOutput schema / properties / coach / description

Previous value: -"The coaching context: coach_id (GoldAvatar's conversation), actor, role, seat, page_url, feed_after (where the coach view starts reading GoldAvatar's feed), picture (the poses' proportions, from GoldAvatar's pose manifest), size_preset, display_mode, the caller's context, and replaced (previous_coach_id, why) when status is replaced: the earlier coaching context was closed or unknown to GoldAvatar Messaging, so a new one was opened"New value: +"The coaching context: coach_id (GoldAvatar's conversation), actor, role, seat, page_url, feed_after (where the coach view starts reading GoldAvatar's feed), picture (the poses the coach view draws the coach from, with their proportions and where their files are, from GoldAvatar's pose manifest), voice (GoldAvatar's voice service), size_preset, display_mode, the caller's context, and replaced (previous_coach_id, why) when status is replaced: the earlier coaching context was closed or unknown to GoldAvatar Messaging, so a new one was opened"

AddedNov 3, 2026

TDQS

A4/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), it discloses the full lifecycle: a session starts on every opening with session_minutes defaulting to 30, the Talk switch is switched on automatically, the host decides the display mode and the view reports what it granted, and GoldSeam stores nothing so the caller must retain the coach object. These are exactly the operational facts an agent could not infer from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded in the first clause, but the middle sentence about fullscreen requests, granted mode and host capabilities is host-behavior detail that does not help tool selection, and several clauses are densely packed into run-on sentences. It is informative but not tight.

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 complex, stateful, session-based tool with seven parameters, nested objects and an output schema, the description covers the session model, follow-up calls and persistence obligations well. It is slightly short on how the session ends or what happens if coach_listen is not called, but most agent needs are met.

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 description coverage is 100%, so role, actor, coach, context, size_preset, display_mode and session_minutes are already documented in the schema, and the description largely restates them, including the same 30-minute and fullscreen defaults. It adds only marginal nuance, such as supplying context 'in any shape' and the reopen-persistence semantics, which the schema already conveys.

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 first sentence gives a specific verb and resource — open a visible, speaking coach as an MCP App view — and enumerates the roles it can take. It does not, however, distinguish itself from the close sibling open_my_coach, which an agent would have to disambiguate on its own.

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 gives clear operational context: the view starts a session, the agent listens with coach_listen through the same turn until time is up, and speaks via coach_say. The gap is that it never states when to prefer this over open_my_coach or coach_board, so sibling routing is left implicit.

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

All goldseam 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.

Open Coach

Tool call template

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources