Fyreflock

Send a line from the chat box

fyreflock_app_say

Sends what the person typed into the chat box, unchanged, to the stranger they are talking to. The box's version of fyreflock_say: a model relaying for the person uses fyreflock_say. Called only by the box with its box_key; without one it is refused with box_only. Nothing is sent on a refusal: no_conversation when nobody is on the other end, not_delivered when they have gone, looks_like_data for contact details or a secret too early. Returns delivered: true and sent_text; replies arrive through the box's socket or fyreflock_app_wait, not here.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "fyreflock_app_say"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	What the person typed into the box, unchanged.
`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.
`message`	No	The refusal, worded for the person.
`delivered`	No
`sent_text`	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": {
+    "delivered": {
+      "const": true,
+      "type": "boolean"
+    },
+    "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"
+    },
+    "sent_text": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields 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."

addedInput schema / properties / text / description

Added value: +"What the person typed into the box, unchanged."

First observedNov 4, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint false, destructiveHint false, openWorldHint true), it discloses that refusals send nothing and enumerates the failure modes: no_conversation, not_delivered, looks_like_data. It also clarifies where replies do not come from, routing the agent to the socket or fyreflock_app_wait.

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-loaded with the core action and free of filler, but the remaining sentences are densely packed run-ons mixing success, refusal, and reply-routing facts. Slightly harder to parse than it needs to be, though every clause carries information.

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 two-parameter send tool with an output schema and annotations already present, the description covers scope, authorization, refusal semantics, and reply path. Nothing an agent needs in order to call it correctly or interpret a failure 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?

Schema coverage is already 100%, so the baseline is 3. The description adds provenance the schema hints at but does not fully explain — the box_key comes from fyreflock_open's result _meta and is held only by the box — which materially constrains who can supply it.

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 — sending the typed chat text unchanged to the stranger on the other end — and explicitly distinguishes itself from the sibling fyreflock_say by naming the relaying-model case. An agent can pick between the two 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?

Gives explicit when-to-use ('called only by the box with its box_key') and an explicit alternative for the other case ('a model relaying for the person uses fyreflock_say'). It also names the refusal condition when the key is absent (box_only), so misuse is predictable.

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.