toolbelt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_TOKEN | No | Optional, for higher GitHub API rate limits. | |
| TOOLBELT_NOTES_DIR | No | Directory the note tools read (default: current directory). |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| github_reposC | List a GitHub user's repositories, newest push first. |
| fetch_urlA | Fetch the text content of a URL (first 10k chars). |
| list_notesA | List note files in the configured notes directory. |
| read_noteB | Read one note by file name from the notes directory. |
| search_notesB | Full-text search across notes; returns file:line matches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a clearly different resource: GitHub repos, arbitrary URLs, and notes files. The only mild overlap is between list_notes (enumerate files) and search_notes (content matches with file:line), but the descriptions make the distinction clear.
Four of five tools follow a verb_noun pattern (fetch_url, list_notes, read_note, search_notes). github_repos breaks the pattern with a noun-only name and abbreviation, a minor deviation in an otherwise predictable set.
Five tools is well within the sweet spot for a small read-only utility server, and each has a distinct job. Nothing feels padded or redundant.
The notes surface is read-only: list, read, and search exist but there is no create_note, update_note, or delete_note, which agents will likely need. Similarly, github_repos exposes only repo listing with no related operations, leaving the toolbelt noticeably one-directional.