organisation.md
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GITHUB_REPO | No | Repository name | organisation.md |
| GITHUB_OWNER | Yes | GitHub username or organisation that owns the repo | |
| GITHUB_TOKEN | Yes | GitHub personal access token with repo scope |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_orgA | Read the full organisation.md file from the GitHub repo. |
| read_sectionA | Read a specific section from organisation.md by heading name. |
| update_sectionB | Propose an update to a section in organisation.md. Creates a pull request for review. |
| propose_changeB | Propose a change to any file in the organisation.md repo. Creates a pull request. |
| search_contextA | Search across organisation.md and CONTEXT/ files for matching text. |
| list_context_filesB | List all files in the CONTEXT/ directory of the repo. |
| import_fileA | import a file (txt, md, docx) into the repo as context. creates a context/ entry and updates the organisation.md index. the ai agent passes file content it has already read. |
| add_infoA | add information to the knowledge base using natural language. describes what to add, and the tool figures out which section and file to put it in. |
| remove_infoB | remove information from the knowledge base using natural language. describes what to remove, and the tool finds and removes it. |
| check_rolesA | check who has what permissions on this repo. reads the codeowners file and current collaborator permissions. |
| configure_codeownersB | update the .github/codeowners file to define who can approve changes to specific paths. |
| check_permissionsA | check if the current user can perform a specific action (add, delete, approve, merge). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| organisation.md - Full Content | The entire organisation.md file with all sections |
| organisation.md - Identity | The Identity section of organisation.md |
| organisation.md - Mission & Vision | The Mission & Vision section of organisation.md |
| organisation.md - Team | The Team section of organisation.md |
| organisation.md - Active Projects | The Active Projects section of organisation.md |
| organisation.md - Decisions | The Decisions section of organisation.md |
| organisation.md - Preferences | The Preferences section of organisation.md |
| organisation.md - Routines | The Routines section of organisation.md |
| organisation.md - Glossary | The Glossary section of organisation.md |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: reading (read_org, read_section), writing via PR (update_section, propose_change), natural language modifications (add_info, remove_info), permissions (check_permissions, check_roles, configure_codeowners), and file management (import_file, list_context_files, search_context). No two tools overlap in functionality.
Tool names consistently follow a verb_noun pattern in snake_case (e.g., add_info, list_context_files, update_section). All names are clear and predictable, with no mixing of conventions.
With 12 tools, the server is well-scoped for its purpose of managing an organisation.md knowledge base and associated context files. Each tool addresses a specific operation, neither too few nor too many.
The tool set covers reading, updating, adding/removing information, searching, importing files, and permissions. Minor gaps include no tool to delete a context file directly (only import and list) and no direct write without PR, but these are reasonable for a review-based workflow.