Fyreflock

Open the Fyreflock chat box

fyreflock_open

Read-only

Open the Fyreflock chat box inside this conversation. The person finds a stranger and talks to them directly in the box, at full speed, and you relay nothing. Call it when they ask to open Fyreflock or the chat box here. If no box appears on this host, say so and offer fyreflock_start instead. Nothing in the result needs summarising, and after it opens you do nothing until they ask you for something else. Returns opened: true, signed_in_as and queue; the box’s own key travels in the result _meta, never in text.

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_open"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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.
`queue`	No
`opened`	No
`message`	No	The refusal, worded for the person.
`signed_in_as`	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": {
+    "error": {
+      "description": "The refusal code, such as no_conversation or rate_limited.",
+      "type": "string"
+    },
+    "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"
+    },
+    "opened": {
+      "const": true,
+      "type": "boolean"
+    },
+    "queue": {
+      "additionalProperties": false,
+      "properties": {
+        "agent_waiting": {
+          "type": "integer"
+        },
+        "text_waiting": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "agent_waiting",
+        "text_waiting"
+      ],
+      "type": "object"
+    },
+    "signed_in_as": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedNov 4, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, yet the description still adds real value: it says nothing needs summarising, the returned key travels in _meta rather than text, and the agent should stay idle afterward. It doesn't explain what happens if a box is already open, which keeps it short of 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.

Conciseness4/5

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

The trigger is front-loaded and the sentences follow a logical order (what it does, when to call, failure path, what to do after). A few phrases ('at full speed', 'you relay nothing', the result-field recap) are slightly redundant given the output schema exists.

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 zero-parameter session-opening action, the description covers purpose, trigger, fallback, post-call behavior, and result shape. Combined with an output schema and read-only annotations, an agent has everything needed to invoke it correctly and know what not to do next.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. No parameter claims in the description are needed or missing.

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 ('Open the Fyreflock chat box inside this conversation') and clarifies the consequence: the person talks to a stranger directly while the agent relays nothing. It differentiates itself from fyreflock_start as a fallback, though it doesn't explicitly contrast with the other in-session siblings like fyreflock_say or fyreflock_leave.

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?

It states the trigger ('Call it when they ask to open Fyreflock or the chat box here'), the fallback path when the box does not appear ('say so and offer fyreflock_start instead'), and the expected posture afterward ('you do nothing until they ask you for something else'). That covers when, when-not, and the alternative.

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.