Skip to main content
Glama

agentleFS

by com.agentlefs
OverviewDiscussionsAdmin

Connect sources

sources_write

Connect GitHub or Google Drive and sync from it. Sync is one-way, into agentleFS, and repeats; a connector-owned path refuses direct edits. Also bind a GitHub issue to a folder or document (safe pointer only — never dumps grant-gated prose onto the issue). Actions — connect: start connecting an EXTERNAL account (provider), not a folder already in agentleFS (browse action=documents lists those); returns a link for the person to authorise in their browser. Only a folder's owner (a manager of some folder) may. sync: point one repository (repo_owner, repo_name, branch) or Drive folder (folder_id) of a connected account at a folder here (location) that you own: a manager of it, or a new top-level folder. vote: vote for a connector that does not exist yet (connector, why); one vote per person, shared with their agents. bind_issue: bind a GitHub issue to a folder or document you can read (issue: URL or owner/repo#N, location or node); returns a safe pointer body to post on the issue — never AFS titles or prose. unbind_issue: remove an issue↔node bind (issue, and/or location or node).

Input Schema

NameRequiredDescriptionDefault
whyNovote: what you would do with it, in one line (at most 200 characters); recorded with the vote
nodeNobind_issue, unbind_issue: folder or document node id, instead of location. A console link (`/d/<Name-Slug>-<32 hex>`, whole or just its id) is accepted too.
seatNothe seat token identity_write action=take_seat gave you; pass it on every call while you drive that agent
issueNobind_issue, unbind_issue: GitHub issue URL or owner/repo#N (required for bind_issue, of_issue; optional for unbind_issue / github_issues)
actionYeswhat to do; each action takes the arguments its line names
branchNosync: GitHub only: the branch to follow (default: the repo default)
accountNosync: the connected account, exactly as browse action=sources prints it (the installation or account ref)
locationNosync: the FOLDER this source writes into, whole path from the workspace root, e.g. "handbook" or "handbook/vendor" · bind_issue, unbind_issue: folder or document path to bind. A console link (`/d/<Name-Slug>-<32 hex>`, whole or just its id) is accepted too.
providerNoconnect: which source to connect: github, or gdrive for Google Drive · sync: which connected account this source uses
acting_asNoan agent identity below you (its id, from identity_write action=spawn) to make this one call as, with that agent's narrower access; for a helper whose session signs in as its person
connectorNovote: the product to connect, e.g. Notion
folder_idNosync: Google Drive only: the Drive folder id to pull
repo_nameNosync: GitHub only: the repository name
repo_ownerNosync: GitHub only: the repository owner
idempotency_keyNoAny 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.

Output Schema

NameRequiredDescriptionDefault
bindNo
textNothe answer as prose, for an action that answers in prose
voteNo
bindsNo
actionYesthe action that answered
wantedNo
unboundNo
availableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. Changed7 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
-  "connect",
-  "sync",
-  "vote"
-]New value: +[
+  "connect",
+  "sync",
+  "vote",
+  "bind_issue",
+  "unbind_issue"
+]
    • addedInput schema / properties / issue
      Added value: +{
+  "description": "bind_issue, unbind_issue: GitHub issue URL or owner/repo#N (required for bind_issue, of_issue; optional for unbind_issue / github_issues)",
+  "type": "string"
+}
    • changedInput schema / properties / location / description
      Previous value: -"sync: the FOLDER this source writes into, whole path from the workspace root, e.g. \"handbook\" or \"handbook/vendor\""New value: +"sync: the FOLDER this source writes into, whole path from the workspace root, e.g. \"handbook\" or \"handbook/vendor\" · bind_issue, unbind_issue: folder or document path to bind. A console link (`/d/<Name-Slug>-<32 hex>`, whole or just its id) is accepted too."
    • addedInput schema / properties / node
      Added value: +{
+  "description": "bind_issue, unbind_issue: folder or document node id, instead of location. A console link (`/d/<Name-Slug>-<32 hex>`, whole or just its id) is accepted too.",
+  "type": "string"
+}
    • addedOutput schema / properties / bind
      Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "issue": {
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "folder",
+        "document"
+      ],
+      "type": "string"
+    },
+    "location": {
+      "type": "string"
+    },
+    "node": {
+      "type": "string"
+    },
+    "pointer_body": {
+      "type": "string"
+    },
+    "pointer_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "issue",
+    "node",
+    "location",
+    "kind",
+    "pointer_url",
+    "pointer_body"
+  ],
+  "type": "object"
+}
    • addedOutput schema / properties / binds
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "issue": {
+        "type": "string"
+      },
+      "kind": {
+        "enum": [
+          "folder",
+          "document"
+        ],
+        "type": "string"
+      },
+      "location": {
+        "type": "string"
+      },
+      "node": {
+        "type": "string"
+      },
+      "pointer_body": {
+        "type": "string"
+      },
+      "pointer_url": {
+        "type": "string"
+      }
+    },
+    "required": [
+      "issue",
+      "node",
+      "location",
+      "kind",
+      "pointer_url",
+      "pointer_body"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}
    • addedOutput schema / properties / unbound
      Added value: +{
+  "type": "boolean"
+}
  3. Changed1 schema field changed
    • addedInput schema / properties / seat
      Added value: +{
+  "description": "the seat token identity_write action=take_seat gave you; pass it on every call while you drive that agent",
+  "maxLength": 64,
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / acting_as
      Added value: +{
+  "description": "an agent identity below you (its id, from identity_write action=spawn) to make this one call as, with that agent's narrower access; for a helper whose session signs in as its person",
+  "type": "string"
+}
  5. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare this is a non-read-only, open-world, non-destructive, non-idempotent write tool; the description adds substantial behavior beyond that: sync is one-way and repeating, connector-owned paths refuse direct edits, connect returns a browser authorization link, bind_issue returns a safe pointer body and never leaks AFS titles or prose, and permissions are tied to folder ownership.

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?

The description is long, but the length is justified by five actions and fifteen parameters. It is front-loaded with the core purpose and then organized as an action-by-action list, with each clause carrying operational detail rather than 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?

Given the tool's complexity, the description covers all five actions, their key arguments, permissions, and important behavioral caveats. An output schema exists, so return-shape details need not be repeated, and the annotations cover safety hints; the description fills the remaining gaps effectively.

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 description coverage is 100%, so the parameter documentation baseline is 3. The description improves on that by grouping parameters by action (for example sync uses repo_owner/repo_name/branch or folder_id plus location, and bind_issue uses issue plus location/node) and by adding ownership and safety constraints that are not fully conveyed by the schema alone.

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 states specific operations (connect, sync, vote, bind_issue, unbind_issue) over specific resources (GitHub, Google Drive, issues, folders/documents), not merely a vague write. It also distinguishes what it is not, e.g. connect is for an external account rather than a folder already in agentleFS, pointing to browse action=documents as the alternative.

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?

Each action is given an explicit use condition: connect starts an external-account connection, sync points a repo or Drive folder at a location, vote is only for connectors that do not exist yet, bind_issue binds an issue to a readable folder or document, and unbind_issue removes that binding. It also names prerequisites and alternatives such as browse action=documents for existing agentleFS folders.

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

All agentleFS toolsInspect
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