Skip to main content
Glama
Sign In

Fyreflock

by io.github.FuloxDev
OverviewDiscussionsAdmin

List the person’s Roosts

fyreflock_roosts
Read-only

List the Roosts (group rooms) this person belongs to, with the roost_id every other Roost tool takes. Call it before fyreflock_roost_read or fyreflock_roost_say when you have no roost_id; a room they are not in yet needs fyreflock_roost_join with an invite code instead. Some are end-to-end encrypted with a key Fyreflock has never held, and those are marked locked: say so plainly rather than pretending they do not exist, and tell them the owner can open a Roost to assistants from the website. Reading nothing here does not mean they have no Roosts.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
roostsYes

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": {
+    "roosts": {
+      "items": {
+        "additionalProperties": false,
+        "properties": {
+          "locked_reason": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "members": {
+            "type": "integer"
+          },
+          "name": {
+            "type": "string"
+          },
+          "readable": {
+            "description": "false when the key never reached Fyreflock, so nothing here can read it.",
+            "type": "boolean"
+          },
+          "roost_id": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "roost_id",
+          "name",
+          "members",
+          "readable",
+          "locked_reason"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "roosts"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered; the description adds substantially beyond that. It discloses end-to-end encrypted 'locked' Roosts whose key Fyreflock never held, prescribes how to report them honestly, and warns that an empty read does not imply the person has no Roosts.

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 purpose and the roost_id rationale, then escalation to alternatives, then the locked-room caveat. It is a dense paragraph with no filler sentences, though the locked-room guidance could be split for faster scanning.

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?

An output schema exists, so the description need not enumerate return values, and it instead spends its words on the edge cases an agent would otherwise get wrong: locked encrypted rooms and the false-negative empty result. Nothing needed to call it correctly 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 the baseline is 4 and there is nothing parameter-related for the description to clarify. It does implicitly characterize the payload by promising a roost_id usable by sibling tools, which is useful framing even though the input schema is empty.

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 and resource ('List the Roosts (group rooms) this person belongs to') and defines the unfamiliar term 'Roosts' inline. It also names the key field returned (roost_id), which distinguishes it from every other Roost tool that consumes that id.

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 routing: call this before fyreflock_roost_read or fyreflock_roost_say when no roost_id is available, and use fyreflock_roost_join with an invite code for rooms the person is not in. Both the when-to-use and the when-to-use-something-else cases are stated.

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