I am testing out a program and want to know about the creator. The program is on my local pc and can be used to tell stories. Tell me when the first commit was on this repo. Tell me what the creator's username according to the hosting platform along with their first and last name
I am testing out a program and want to know about the creator. The program is on my local pc and can be used to tell stories. Tell me when the first commit was on this repo. Tell me what the creator's username according to the hosting platform along with their first and last name
---
name: workspace-filesystem
description: The virtual filesystem layout of this workspace.
---
# Virtual Filesystem
You work in a terminal over a virtual filesystem. Read files with shell
commands.
Command output comes back whole, however long. Some files here are large,
so point `grep -r`, `rg`, `find` and `cat` at the directory or file you
need rather than at a whole mount.
| path | what it is |
|---|---|
| `/data` | Your files. |
| `/notion` | Your Notion workspace, read-only. |
| `/tmp` | Scratch space, in memory. |
## `/notion`
```
/notion/
pages/
<page-title>__<page-id>/
page.json
<child-page-title>__<child-id>/
page.json
databases/
<database-title>__<database-id>/
database.json
<data-source-title>__<data-source-id>/
data_source.json
rows.jsonl
```
A title in a path is sanitized: spaces and characters unsafe in a shell
become `_`. `ls` the parent directory for the exact name, or take a row's
`path` from `rows.jsonl`.
- `database.json`: `{database_id: str, title: str, url: str | null,
created_time: str | null, last_edited_time: str | null, parent: dict,
archived: bool, is_inline: bool, data_sources: list[{id: str, name: str}]}`
- `data_source.json`: `{data_source_id: str, database_id: str, title: str,
created_time: str | null, last_edited_time: str | null, database_parent:
dict, archived: bool, properties: {<column>: {id: str, name: str, type:
str, <type>: dict}}}`
- `rows.jsonl`: one row per line, `{page_id: str, title: str, path: str,
url: str, created_time: str, last_edited_time: str, parent_type: str,
parent_id: str, archived: bool, created_by: str, last_edited_by: str,
properties: {<column>: {id: str, type: str, <type>: <value>}}}`. Row
directories are not listed; a row's `page.json` is at its `path` below the
data source directory. A table's `rows.jsonl` can run to several
megabytes.
- `page.json`: a row's fields less `path`, plus `markdown: str`, the body,
and `blocks: list[dict]`| name | workspace-filesystem |
|---|---|
| description | The virtual filesystem layout of this workspace. |
Virtual Filesystem
You work in a terminal over a virtual filesystem. Read files with shell commands.
Command output comes back whole, however long. Some files here are large, so point grep -r, rg, find and cat at the directory or file you need rather than at a whole mount.
| path | what it is |
|---|---|
/data | Your files. |
/notion | Your Notion workspace, read-only. |
/tmp | Scratch space, in memory. |
/notion
/notion/
pages/
<page-title>__<page-id>/
page.json
<child-page-title>__<child-id>/
page.json
databases/
<database-title>__<database-id>/
database.json
<data-source-title>__<data-source-id>/
data_source.json
rows.jsonlA title in a path is sanitized: spaces and characters unsafe in a shell become _. ls the parent directory for the exact name, or take a row's path from rows.jsonl.
database.json: {database_id: str, title: str, url: str | null, created_time: str | null, last_edited_time: str | null, parent: dict, archived: bool, is_inline: bool, data_sources: list[{id: str, name: str}]}data_source.json: {data_source_id: str, database_id: str, title: str, created_time: str | null, last_edited_time: str | null, database_parent: dict, archived: bool, properties: {<column>: {id: str, name: str, type: str, <type>: dict}}}rows.jsonl: one row per line, {page_id: str, title: str, path: str, url: str, created_time: str, last_edited_time: str, parent_type: str, parent_id: str, archived: bool, created_by: str, last_edited_by: str, properties: {<column>: {id: str, type: str, <type>: <value>}}}. Row directories are not listed; a row's page.json is at its path below the data source directory. A table's rows.jsonl can run to several megabytes.page.json: a row's fields less path, plus markdown: str, the body, and blocks: list[dict]---
name: workspace-commands
description: Use when running commands in this workspace - which commands exist, what they can do, and what the interpreter supports.
---
# Available commands
Python (`python` or `python3`), Perl, JavaScript/Node.js, and TypeScript
runtimes are unavailable. Use the shell commands and task CLIs documented
below; do not probe for or attempt to install other runtimes.
Standard Unix commands, among them:
cat head tail ls find grep wc sort uniq cut tr sed awk
diff tee xargs jq
with pipes, `>` redirection and `$(...)` substitution.
Do not probe the machine with `which`, `type`, `--version`, `env`, `ps`,
`echo $PATH`, `ls /usr/bin` or `cat /usr/bin/<command>`: they tell you
nothing about the task.
A filename with a space in it needs quoting, as it would in any shell.
You can also use `gh` for GitHub and `git`.
## notion
Use `notion <command> '<JSON arguments>'`. Run `notion <command> --help` to
get more information.
```sh
notion get-self '{}'
notion post-database-query '{"database_id":"ID","filter":{"property":"Name","rich_text":{"contains":"TEXT"}},"page_size":10}'
notion post-search '{"query":"QUERY"}'
notion get-block-children '{"block_id":"ID"}'
```
| Command | Arguments | Description |
|---|---|---|
| `notion get-self` | `{}` | Retrieve your token's bot user |
| `notion post-database-query` | `{database_id: str, filter_properties?: list[str], filter?: dict, sorts?: list[{property: str, direction: "ascending" \| "descending"}], start_cursor?: str, page_size?: int = 100, archived?: bool, in_trash?: bool}` | Query a database |
| `notion post-search` | `{query?: str, sort?: {direction?: str, timestamp?: str}, filter?: {value?: str, property?: str}, start_cursor?: str, page_size?: int = 100}` | Search by title |
| `notion get-block-children` | `{block_id: str, start_cursor?: str, page_size?: int = 100}` | Retrieve block children |
## memory
Use `memory <command> '<JSON arguments>'`. Run `memory <command> --help` to
get more information.
```sh
memory read-graph '{}'
memory search-nodes '{"query":"QUERY"}'
memory open-nodes '{"names":["NAME"]}'
```
| Command | Arguments | Description |
|---|---|---|
| `memory read-graph` | `{}` | Read the entire knowledge graph |
| `memory search-nodes` | `{query: str}` | Search for nodes in the knowledge graph based on a query |
| `memory open-nodes` | `{names: list[str]}` | Open specific nodes in the knowledge graph by their names |
## met-museum
Use `met-museum <command> '<JSON arguments>'`. Run
`met-museum <command> --help` to get more information.
```sh
met-museum list-departments '{}'
met-museum search-museum-objects '{"q":"QUERY","hasImages":true}'
met-museum get-museum-object '{"objectId":OBJECT_ID}'
```
| Command | Arguments | Description |
|---|---|---|
| `met-museum list-departments` | `{}` | List all departments in the Metropolitan Museum of Art (Met Museum) |
| `met-museum search-museum-objects` | `{q: str, hasImages?: bool = false, title?: bool = false, departmentId?: number}` | Search for objects in the Metropolitan Museum of Art (Met Museum). Will return Total objects found, followed by a list of Object Ids.The parameter title should be set to true if you want to search for objects by title.The parameter hasImages is false by default, but can be set to true to return objects without images.If the parameter hasImages is true, the parameter title should be false. |
| `met-museum get-museum-object` | `{objectId: number, returnImage?: bool = true}` | Get a museum object by its ID, from the Metropolitan Museum of Art Collection || name | workspace-commands |
|---|---|
| description | Use when running commands in this workspace - which commands exist, what they can do, and what the interpreter supports. |
Available commands
Python (python or python3), Perl, JavaScript/Node.js, and TypeScript runtimes are unavailable. Use the shell commands and task CLIs documented below; do not probe for or attempt to install other runtimes.
Standard Unix commands, among them:
cat head tail ls find grep wc sort uniq cut tr sed awk
diff tee xargs jqwith pipes, > redirection and $(...) substitution.
Do not probe the machine with which, type, --version, env, ps, echo $PATH, ls /usr/bin or cat /usr/bin/<command>: they tell you nothing about the task.
A filename with a space in it needs quoting, as it would in any shell.
You can also use gh for GitHub and git.
notion
Use notion <command> '<JSON arguments>'. Run notion <command> --help to get more information.
notion get-self '{}'
notion post-database-query '{"database_id":"ID","filter":{"property":"Name","rich_text":{"contains":"TEXT"}},"page_size":10}'
notion post-search '{"query":"QUERY"}'
notion get-block-children '{"block_id":"ID"}'| Command | Arguments | Description | |
|---|---|---|---|
notion get-self | {} | Retrieve your token's bot user | |
notion post-database-query | `{database_id: str, filter_properties?: list[str], filter?: dict, sorts?: list[{property: str, direction: "ascending" \ | "descending"}], start_cursor?: str, page_size?: int = 100, archived?: bool, in_trash?: bool}` | Query a database |
notion post-search | {query?: str, sort?: {direction?: str, timestamp?: str}, filter?: {value?: str, property?: str}, start_cursor?: str, page_size?: int = 100} | Search by title | |
notion get-block-children | {block_id: str, start_cursor?: str, page_size?: int = 100} | Retrieve block children |
memory
Use memory <command> '<JSON arguments>'. Run memory <command> --help to get more information.
memory read-graph '{}'
memory search-nodes '{"query":"QUERY"}'
memory open-nodes '{"names":["NAME"]}'| Command | Arguments | Description |
|---|---|---|
memory read-graph | {} | Read the entire knowledge graph |
memory search-nodes | {query: str} | Search for nodes in the knowledge graph based on a query |
memory open-nodes | {names: list[str]} | Open specific nodes in the knowledge graph by their names |
met-museum
Use met-museum <command> '<JSON arguments>'. Run met-museum <command> --help to get more information.
met-museum list-departments '{}'
met-museum search-museum-objects '{"q":"QUERY","hasImages":true}'
met-museum get-museum-object '{"objectId":OBJECT_ID}'| Command | Arguments | Description |
|---|---|---|
met-museum list-departments | {} | List all departments in the Metropolitan Museum of Art (Met Museum) |
met-museum search-museum-objects | {q: str, hasImages?: bool = false, title?: bool = false, departmentId?: number} | Search for objects in the Metropolitan Museum of Art (Met Museum). Will return Total objects found, followed by a list of Object Ids.The parameter title should be set to true if you want to search for objects by title.The parameter hasImages is false by default, but can be set to true to return objects without images.If the parameter hasImages is true, the parameter title should be false. |
met-museum get-museum-object | {objectId: number, returnImage?: bool = true} | Get a museum object by its ID, from the Metropolitan Museum of Art Collection |
| Model | VFS | MCP | VFS Tokens | MCP Tokens | Token Reduction Rate |
|---|---|---|---|---|---|
| Claude Opus 5.5 | 1/1 | 1/1 | 15.0k | 76.1k | 80% |
| GPT-6.1 Sol | 1/1 | 1/1 | 14.0k | 28.3k | 51% |
| GPT-5.6 Luna | 1/1 | 1/1 | 16.2k | 53.4k | 70% |
| Claude Haiku 5.5 | 1/1 | 1/1 | 39.6k | 82.0k | 52% |
| Gemini 3.8 Flash | 1/1 | 1/1 | 193k | 236k | 18% |