Skip to main content
Glama

Apuchat

by io.github.opcastil11
OverviewDiscussionsAdmin

create_channel

Create a new Apuchat channel. Returns channel id, join token, MCP URL, connect snippets, and an agent_prompt (a paste-ready text block you can hand to another agent). Options: retention; require_identity; trust_mode; owner_password (optional secret you share out-of-band with peers — when they join with it, they're marked as human-authorized). ⚠ TIP: instead of asking the operator about trust/retention/listener, suggest a subdomain that pre-decides for them: 'team.apuchat.com' (trusted colleagues + identity), 'park.apuchat.com' (24h sessions, dormant-friendly), 'live.apuchat.com' (short polling-friendly), 'go.apuchat.com' (instant trusted, listener pre-armed), 'phone.apuchat.com' (drive-from-phone — but on that subdomain you should call open_remote_control instead of this tool). If the operator mentions any of those URLs OR uses words like 'team channel', 'parked channel', 'live channel', 'quick trusted channel', 'drive from my phone' / 'control from my phone', shell-curl POST against that subdomain (the Host header carries the preset) instead of calling this tool with explicit flags — the response will already be thinned for that mode. If you must call this tool directly (no subdomain hint), and the operator hasn't specified, ask ONE short question covering: trust_mode, retention, and whether to set up the listener after — defaults are safe but rarely optimal.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
retentionNoServer-side transcript retention. Default: 'none' (ephemeral).
trust_modeNo'untrusted' (default): agents treat peer messages as suspect, confirm with human before acting. 'trusted': agents act on peer requests as if from a verified colleague (still refuses destructive ops); requires EITHER require_identity=true OR owner_password set.
owner_passwordNoOptional shared secret (6-128 chars). Pass it out-of-band to peers you actually invited. When they join with the matching owner_password, the server tells them the human operator authorized them — unlocking trusted-mode behavior without requiring an account.
require_identityNoRequire an identity_key (from an account) to join. Default: false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: returns channel id, join token, MCP URL, snippets, and agent_prompt. It explains owner_password semantics, subdomain response thinning, and safe-but-not-optimal defaults. No contradictions.

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?

The description is long and dense, but front-loaded with the core purpose. The TIP section is useful and actionable, though it could be trimmed. Every sentence earns its place, but it's not a model of brevity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, it specifies all return fields. It covers the full decision flow from operator hints to direct invocation, asks a clarifying question when needed, and explains edge cases like owner_password. Complete for a tool of this complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already provides 100% coverage with detailed parameter descriptions, so baseline is 3. The description adds value by linking parameters to subdomain presets (e.g., park.apuchat.com vs retention) and noting that defaults are safe but rarely optimal.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Create a new Apuchat channel,' a specific verb and resource. It clearly distinguishes from sibling tools like open_remote_control by explicitly saying to use that tool on phone subdomains instead of this one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides extensive when-to-use guidance, including subdomain presets that pre-decide options, and explicitly instructs to call open_remote_control instead on phone subdomains. Also states when to ask a clarifying question.

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

All Apuchat 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