Fyreflock

Socket ticket for the chat box

fyreflock_app_ticket

Read-only

Mints a one-minute, single-use ticket the chat box presents on its WebSocket upgrade, with the ICE servers for a peer-to-peer line. Called by the box itself right after fyreflock_open, never by a model: box_key is the key fyreflock_open handed the box in its result _meta, and a call without a valid one is refused with box_only (a model relays with fyreflock_say and fyreflock_listen instead). Returns ticket, ws_url, ice_servers, chat_in_pane and early_access; a ticket already used or older than a minute fails the upgrade, so the box mints a fresh one per connection.

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

Input Schema

Name	Required	Description	Default
`box_key`	No	The key the chat box received in fyreflock_open's result _meta. Only the box holds one, so only the box can call this tool.

Output Schema

Name	Required	Description
`ok`	No	Only on a refusal, as false: error and message then say why, and nothing else is set.
`error`	No	The refusal code, such as no_conversation or rate_limited.
`ticket`	No	Presented once, within a minute, on the WebSocket upgrade.
`ws_url`	No
`message`	No	The refusal, worded for the person.
`ice_servers`	No
`chat_in_pane`	No	true when the person already has Fyreflock open in the pane beside a Claude Code session.
`early_access`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "chat_in_pane": {
+      "description": "true when the person already has Fyreflock open in the pane beside a Claude Code session.",
+      "type": "boolean"
+    },
+    "early_access": {
+      "type": "boolean"
+    },
+    "error": {
+      "description": "The refusal code, such as no_conversation or rate_limited.",
+      "type": "string"
+    },
+    "ice_servers": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "credential": {
+            "type": "string"
+          },
+          "urls": {},
+          "username": {
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "message": {
+      "description": "The refusal, worded for the person.",
+      "type": "string"
+    },
+    "ok": {
+      "const": false,
+      "description": "Only on a refusal, as false: error and message then say why, and nothing else is set.",
+      "type": "boolean"
+    },
+    "ticket": {
+      "description": "Presented once, within a minute, on the WebSocket upgrade.",
+      "type": "string"
+    },
+    "ws_url": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 4, 2026

changedInput schema / properties / box_key / description

Previous value: -"Set by the chat box itself."New value: +"The key the chat box received in fyreflock_open's result _meta. Only the box holds one, so only the box can call this tool."

First observedNov 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: one-minute TTL, single-use semantics, the box_only refusal for a missing or invalid box_key, the fact that a used or expired ticket fails the upgrade, and that a fresh ticket is minted per connection. It also enumerates the return payload (ticket, ws_url, ice_servers, chat_in_pane, early_access). That is the full failure and lifecycle profile an agent needs.

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?

Front-loads the core action and packs lifecycle, refusal, and return details into one dense paragraph with no filler. It is a long run-on sentence with stacked parentheticals, so slight restructuring would improve scannability, but nothing is wasted.

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?

For a single-parameter, read-only ticket mint, the description covers caller identity, prerequisite (right after fyreflock_open), failure modes, and payload. Listing return fields is mildly redundant with the output schema, but it reinforces routing rather than substituting for documentation.

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 coverage is 100% and the schema already explains box_key, so the baseline is 3. The description adds real meaning: it ties box_key to fyreflock_open's result _meta and clarifies that omitting it is refused with box_only — useful given the schema lists zero required parameters and would otherwise imply the call is optional.

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?

States a specific verb and resource — mints a one-minute, single-use ticket presented on WebSocket upgrade, plus ICE servers for a peer-to-peer line. It also distinguishes itself from the model-facing siblings by naming fyreflock_say and fyreflock_listen as the model's route, so an agent can place it without opening any schema.

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?

Gives explicit timing (called by the box itself right after fyreflock_open), an explicit exclusion (never by a model), and a named alternative path (relay with fyreflock_say and fyreflock_listen). That covers when, when-not, and the fallback in one sentence.

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

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