Fyreflock

Check Fyreflock

fyreflock_status

Read-only

Check the person's Fyreflock state: whether the campfire (matching hours) is open, how many people are waiting right now, and whether a conversation is already open. Call this first when you have no conversation_id; it never waits and never joins a queue, which fyreflock_start does. If campfire_open is false, tell them when campfire_opens_at and do not call fyreflock_start. If first_run comes back, show it to the person once, word for word: it tells them how to stop their assistant asking permission for every single message. Being connected is being signed in, so there is no signed-out case. Returns: signed_in_as, campfire_open, campfire_opens_at, queue {agent_waiting, text_waiting}, conversation_id (null when none is open), parked, first_run.

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

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
`parked`	No	A search kept running for a chat box that was closed mid-search, or null.
`message`	No	The refusal, worded for the person.
`first_run`	No
`signed_in_as`	No
`campfire_open`	No
`conversation_id`	No
`campfire_opens_at`	No	Unix milliseconds, when the campfire is out.

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": {
+    "campfire_open": {
+      "type": "boolean"
+    },
+    "campfire_opens_at": {
+      "description": "Unix milliseconds, when the campfire is out.",
+      "type": [
+        "number",
+        "null"
+      ]
+    },
+    "conversation_id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "The refusal code, such as no_conversation or rate_limited.",
+      "type": "string"
+    },
+    "first_run": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "parked": {
+      "description": "A search kept running for a chat box that was closed mid-search, or null."
+    },
+    "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.8/5.0

Behavior5/5

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

Annotations only declare it as a safe read; the description adds real behavioral context: it never blocks or queues, there is no signed-out state so the agent should not look for one, and first_run must be shown verbatim exactly once. These are non-obvious operational rules an agent could not infer from readOnlyHint/destructiveHint alone.

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?

Purpose is front-loaded and the ordering follows what an agent needs to decide and then act. It is denser than ideal — several clauses are packed into single sentences (the signed-in/signed-out aside, the first_run verbatim rule) — but each clause carries operating instructions rather than filler.

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 status check, the description covers everything that matters: when to call it, that it cannot block, what happens when the campfire is closed, and how to handle first_run. The inline field list is mildly redundant with the output schema but functions as an at-a-glance contract, and no prerequisite is missing.

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 per the baseline this is a 4. The description does not need to explain inputs, and the schema is empty by design.

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 a specific verb+resource ("Check the person's Fyreflock state") and immediately enumerates what that state comprises: campfire open status, queue depth, and whether a conversation exists. It also names the sibling it is not (fyreflock_start), so an agent can route between them without opening either 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?

Explicit sequencing rule ("Call this first when you have no conversation_id"), explicit exclusion ("it never waits and never joins a queue, which fyreflock_start does"), and an explicit conditional instruction ("If campfire_open is false ... do not call fyreflock_start"). Both when-to-use and when-not-to-use are covered, plus the alternative is named.

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.