phygital-brain
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| prompts | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| phygital_brain_startA | Start a Phygital Brain job: returns that job's step-by-step instructions (a skill) as text, for you to follow. It changes nothing by itself: you then build or change the person's brain with your own file tools, in the folder they chose. Call it first when the person says 'set up my second brain', 'upgrade my second brain', 'set up my team', 'set up my brain keeper', 'translate Phygital Brain into my language', 'switch my brain to another language', or the same in another language. Calling it again returns the same instructions. To open a file the instructions name, use phygital_brain_read_file; to see which files exist, use phygital_brain_list_files. An unknown job returns an error naming the valid ones. |
| phygital_brain_read_fileA | Read one of Phygital Brain's own files and return its full text: a form, a template, a language file or a skill. Use it when the instructions from phygital_brain_start name a file; if you don't know the exact name, list the folder with phygital_brain_list_files first. A missing file, a folder, or a path outside the skills folder returns an error that says so. It reads only Phygital Brain's files, never the person's brain, and changes nothing. |
| phygital_brain_list_filesA | List what's in one of Phygital Brain's folders: one name per line, sorted, with folders ending in '/'. It doesn't look inside subfolders: list a subfolder to see its files. Use it to find a file's exact name, then open the file with phygital_brain_read_file. A folder that doesn't exist returns an error. It reads only Phygital Brain's files, never the person's brain, and changes nothing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| set-up-my-second-brain | Build a Phygital Brain in the folder you chose. |
| brain-keeper | Set up, update or move the Brain Keeper. |
| add-language | Make Phygital Brain in a new language, or switch a brain's language. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: list_files enumerates directory contents, read_file returns a single file's text, and start provides job instructions. There is no overlap in function, and the descriptions make the intended use and dependencies explicit.
All tools share the predictable phygital_brain_ prefix and use snake_case. However, two tools follow a verb_noun pattern (list_files, read_file) while start is a bare verb, a minor deviation from strict consistency.
Three tools are well-matched to the server's narrow purpose of delivering instructions and reading its own files. Each tool is necessary, and the count avoids redundancy while remaining sufficient for the task.
The surface covers the full lifecycle needed for this read-only helper: start a job to get instructions, list relevant files, and read their contents. No critical gaps exist, and the server intentionally avoids write operations, which are delegated to the user's own tools.