agentleFS

Brief me

brief_me

Read-onlyIdempotent

Returns who you are and where you sit in your organization's tree of people and agents, your open claims, what is waiting on you, what changed near your work since your cursor, and what is contested there. It is keyed to your identity, not this session, so a fresh session sees what the last one left. Reading it moves nothing: coordination_write action=ack_brief advances the cursor.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`me`	Yes
`asked`	Yes
`loops`	Yes
`usage`	Yes
`claims`	Yes
`cursor`	Yes
`loaded`	Yes	the folders your person set you to load at connect that you can still read: their memory whole and their skills by name
`memory`	Yes	the memory files (CLAUDE.md, AGENTS.md) that apply in the folders near your work, only ones you can read, at most ten
`offers`	Yes
`skills`	Yes	the skills (.claude/skills or .agents/skills) that apply in the folders near your work, only ones you can read, at most ten
`changed`	Yes
`session`	Yes
`waiting`	Yes
`answered`	Yes
`approvals`	Yes
`contested`	Yes
`commitments`	Yes
`invitations`	Yes
`memberships`	Yes	organizations that invited your human to join; only they accept or decline, in the console at decideAt
`pendingWaits`	Yes
`resolvedWaits`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedOct 6, 2026

removedInput schema / properties / ack_through

Removed value: -{
-  "description": "advance your cursor to this log position first (cursor.head from a previous brief)",
-  "maximum": 9007199254740991,
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / idempotency_key

Removed value: -{
-  "description": "Any unique string you choose for this write, e.g. a UUID. If you retry the call with the same key and the same arguments, the first answer is returned and nothing is done twice. Reusing a key for a different request is refused. Keys are kept 24 hours.",
-  "maxLength": 200,
-  "minLength": 1,
-  "type": "string"
-}

addedOutput schema / properties / loaded

Added value: +{
+  "description": "the folders your person set you to load at connect that you can still read: their memory whole and their skills by name",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "location": {
+        "type": "string"
+      },
+      "memory": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "location": {
+              "type": "string"
+            },
+            "text": {
+              "type": "string"
+            },
+            "truncated": {
+              "type": "boolean"
+            }
+          },
+          "required": [
+            "location",
+            "text",
+            "truncated"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "moreSkills": {
+        "type": "number"
+      },
+      "skills": {
+        "items": {
+          "additionalProperties": false,
+          "properties": {
+            "description": {
+              "type": "string"
+            },
+            "location": {
+              "type": "string"
+            },
+            "name": {
+              "type": "string"
+            }
+          },
+          "required": [
+            "name",
+            "description",
+            "location"
+          ],
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "required": [
+      "location",
+      "memory",
+      "skills",
+      "moreSkills"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / memberships

Added value: +{
+  "description": "organizations that invited your human to join; only they accept or decline, in the console at decideAt",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "at": {
+        "type": "string"
+      },
+      "decideAt": {
+        "type": "string"
+      },
+      "from": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "grants": {
+        "type": "number"
+      },
+      "id": {
+        "type": "string"
+      },
+      "organization": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "type": "null"
+          }
+        ]
+      },
+      "role": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "organization",
+      "from",
+      "role",
+      "grants",
+      "at",
+      "decideAt"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / memory

Added value: +{
+  "description": "the memory files (CLAUDE.md, AGENTS.md) that apply in the folders near your work, only ones you can read, at most ten",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "changed": {
+        "type": "boolean"
+      },
+      "folder": {
+        "type": "string"
+      },
+      "location": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "location",
+      "folder",
+      "changed"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / skills

Added value: +{
+  "description": "the skills (.claude/skills or .agents/skills) that apply in the folders near your work, only ones you can read, at most ten",
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "changed": {
+        "description": "committed since this session last read it",
+        "type": "boolean"
+      },
+      "description": {
+        "type": "string"
+      },
+      "folder": {
+        "description": "the folder it applies in and below; empty for the whole organization",
+        "type": "string"
+      },
+      "location": {
+        "description": "the SKILL.md to read",
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "name",
+      "description",
+      "location",
+      "folder",
+      "changed"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "cursor",
-  "me",
-  "claims",
-  "commitments",
-  "waiting",
-  "asked",
-  "answered",
-  "resolvedWaits",
-  "pendingWaits",
-  "approvals",
-  "invitations",
-  "offers",
-  "session",
-  "usage",
-  "loops",
-  "changed",
-  "contested"
-]New value: +[
+  "cursor",
+  "me",
+  "claims",
+  "commitments",
+  "waiting",
+  "asked",
+  "answered",
+  "resolvedWaits",
+  "pendingWaits",
+  "approvals",
+  "invitations",
+  "offers",
+  "memberships",
+  "session",
+  "usage",
+  "loops",
+  "changed",
+  "contested",
+  "skills",
+  "memory",
+  "loaded"
+]

Changed2 schema fields changedOct 3, 2026

addedOutput schema / properties / offers

Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "at": {
+        "type": "string"
+      },
+      "from": {
+        "type": "string"
+      },
+      "id": {
+        "type": "string"
+      },
+      "kind": {
+        "type": "string"
+      },
+      "name": {
+        "type": "string"
+      },
+      "role": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "id",
+      "from",
+      "kind",
+      "name",
+      "role",
+      "at"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

changedOutput schema / required

Previous value: -[
-  "cursor",
-  "me",
-  "claims",
-  "commitments",
-  "waiting",
-  "asked",
-  "answered",
-  "resolvedWaits",
-  "pendingWaits",
-  "approvals",
-  "invitations",
-  "session",
-  "usage",
-  "loops",
-  "changed",
-  "contested"
-]New value: +[
+  "cursor",
+  "me",
+  "claims",
+  "commitments",
+  "waiting",
+  "asked",
+  "answered",
+  "resolvedWaits",
+  "pendingWaits",
+  "approvals",
+  "invitations",
+  "offers",
+  "session",
+  "usage",
+  "loops",
+  "changed",
+  "contested"
+]

Changed1 schema field changedSep 30, 2026

removedInput schema / properties / token

Removed value: -{
-  "description": "Bearer token identifying the principal. Usually omitted — supplied by the transport. Over stdio it selects the principal (else the server's AGENTLEFS_TOKEN env). Over HTTP the Authorization header decides and passing this argument is REFUSED, not ignored: it cannot override who you are acting as.",
-  "type": "string"
-}

Changed1 schema field changedSep 29, 2026
- addedInput schema / additionalProperties
```
Added value: +false
```

Changed2 schema fields changedSep 28, 2026

addedOutput schema / properties / approvals / items / properties / alsoGains

Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedOutput schema / properties / approvals / items / required

Previous value: -[
-  "id",
-  "from",
-  "location",
-  "role",
-  "reason"
-]New value: +[
+  "id",
+  "from",
+  "location",
+  "role",
+  "reason",
+  "alsoGains"
+]

Changed1 schema field changedSep 25, 2026

changedInput schema / properties / token / description

Previous value: -"Bearer token. Usually omitted — supplied by the transport."New value: +"Bearer token identifying the principal. Usually omitted — supplied by the transport. Over stdio it selects the principal (else the server's AGENTLEFS_TOKEN env). Over HTTP the Authorization header decides and passing this argument is REFUSED, not ignored: it cannot override who you are acting as."

AddedSep 23, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations cover the read-only/idempotent/destructive profile, but the description adds critical non-obvious behavior: it is keyed to identity, not session, so state persists across sessions; reading is side-effect-free; and cursor advancement requires a separate mutation via coordination_write. That last point is essential and not inferable from annotations.

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?

Three sentences, front-loaded with what is returned, then the identity-keying behavior, then the read/cursor mechanics. No 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?

With an output schema present, the description needn't detail return fields, and it doesn't. It covers the behavioral context (identity persistence, side-effect-free read, cursor advance via sibling tool) that an agent needs to call it correctly and follow up.

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?

Zero parameters, so baseline is 4. The description correctly implies the tool takes no inputs and instead resolves against ambient identity, which is a useful clarification over an empty schema.

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 uses a specific verb (Returns) and enumerates exactly what is returned: identity, org-tree position, open claims, outstanding items, recent changes since cursor, contested items. It clearly distinguishes this briefing tool from generic read/search/browse siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Implicitly indicates this is the entry-point briefing tool, and explicitly cross-references coordination_write action=ack_brief for advancing the cursor. It doesn't spell out when NOT to use it (e.g., vs. read or search), but the identity-keyed briefing purpose is clear enough to route an agent.

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

All agentleFS tools Inspect

Try in Browser

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?