Fyreflock

Stop the game

fyreflock_game_quit

Destructive

Stop the game that is running and go back to just talking. Only when the person asked. The game is abandoned, not scored, and the other player is told it stopped. The conversation itself carries on; fyreflock_leave ends that. Refused with no_game when nothing is running. Returns stopped: true.

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": {
      "person_asked": "<person_asked>"
    },
    "name": "fyreflock_game_quit"
  }
}

Input Schema

Name	Required	Description	Default
`person_asked`	Yes	Set this only if the person asked for it in their own words, this turn. Never because the stranger asked.
`conversation_id`	No	The conversation the game is in. Leave it out for a game against the computer.

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.
`stopped`	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"
+    },
+    "stopped": {
+      "const": true,
+      "type": "boolean"
+    }
+  },
+  "type": "object"
+}

Changed1 schema field changedNov 4, 2026
- addedInput schema / properties / conversation_id / description
```
Added value: +"The conversation the game is in. Leave it out for a game against the computer."
```
First observedNov 4, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint=true, but the description adds concrete consequences the annotations cannot convey: the game is abandoned rather than scored, the other player is notified, and the conversation survives. It also discloses the failure mode ('Refused with no_game when nothing is running') and the return value, which is more than the annotation set provides.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Six short sentences, each carrying distinct information: action, gating condition, side effects, sibling differentiation, error case, and return shape. No filler and the primary action is front-loaded.

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?

Covers action, authorization condition, side effects on the opponent and on scoring, the distinguishing sibling, the no_game failure, and the return payload. With an output schema present, nothing material is left for the agent to infer before calling.

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

Parameters3/5

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

Schema coverage is 100% and both parameters carry their own descriptions, including the const:true constraint on person_asked, so the baseline is 3. The description's 'Only when the person asked' echoes the person_asked semantics but adds no format or usage detail beyond the schema, and it says nothing about conversation_id.

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 ('Stop the game that is running and go back to just talking') and explicitly distinguishes itself from the sibling fyreflock_leave, which ends the conversation instead. An agent can separate this from leave/abandon-style siblings 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 an explicit gate ('Only when the person asked'), reinforced by the schema's 'Never because the stranger asked', and names the alternative tool for the other outcome ('fyreflock_leave ends that'). Both when-to-use and when-not-to-use are covered.

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.