Skip to main content
Glama
Sign In

Fyreflock

by io.github.FuloxDev
OverviewDiscussionsAdmin

List the games

fyreflock_games
Read-only

List the games two people can play through their assistants, with the game_id the other game tools take. Use this to show the person what is on offer before fyreflock_game_invite (with the stranger they are talking to) or fyreflock_game_solo (alone, while waiting; only where can_play_alone is true). Reading this does not start anything.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
gamesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "games": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "blurb": {
+            "type": "string"
+          },
+          "can_play_alone": {
+            "description": "Whether fyreflock_game_solo can start it against the computer.",
+            "type": "boolean"
+          },
+          "game_id": {
+            "description": "What fyreflock_game_invite and fyreflock_game_solo take.",
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          },
+          "rules": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          }
+        },
+        "required": [
+          "game_id",
+          "name",
+          "blurb",
+          "rules",
+          "can_play_alone"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "games"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and non-destructive, so safety is covered. The description still adds real value by asserting 'Reading this does not start anything', pre-empting the reasonable agent worry that listing a two-player game might open a session, and by flagging that can_play_alone is a per-game field in the output.

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?

Two sentences, front-loaded with the action, then the routing. The second sentence is long and stacks two parentheticals, but every clause carries decision-relevant information, so 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 zero-parameter list tool with an output schema, annotations marking it read-only, and many similar siblings, this gives everything an agent needs: what it returns, why it is called first, and which tool to pick next under which condition.

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 no parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description instead spends its words on the response fields (game_id, can_play_alone) that drive follow-up calls.

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 ('List the games two people can play through their assistants') and adds the key output fact that the response carries the game_id the other tools consume, which is exactly what separates it from join/move/invite siblings.

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?

Explicitly says when to use it (to show the person what is on offer) and names the two downstream siblings with their selecting conditions: fyreflock_game_invite for a stranger, fyreflock_game_solo alone and only where can_play_alone is true. No inference is required.

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

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

Resources