Skip to content

Commit 8991436

Browse files
tobySamMorrowDrums
authored andcommitted
docs: update toolset copy
1 parent 11b1828 commit 8991436

File tree

1 file changed

+5
-12
lines changed

1 file changed

+5
-12
lines changed

Diff for: README.md

+5-12
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ If you don't have Docker, you can use `go build` to build the binary in the
110110

111111
## Tool Configuration
112112

113-
The GitHub MCP Server supports enabling or disabling specific groups of functionalities via the `--toolsets` flag. This allows you to control which GitHub API capabilities are available to your AI tools.
113+
The GitHub MCP Server supports enabling or disabling specific groups of functionalities via the `--toolsets` flag. This allows you to control which GitHub API capabilities are available to your AI tools. Enabling only the toolsets that you need can help the LLM with tool choice and reduce the context size.
114114

115115
### Available Toolsets
116116

@@ -127,7 +127,7 @@ The following sets of tools are available (all are on by default):
127127

128128
#### Specifying Toolsets
129129

130-
To reduce the available tools, you can pass an allow-list in two ways:
130+
To specify toolsets you want available to the LLM, you can pass an allow-list in two ways:
131131

132132
1. **Using Command Line Argument**:
133133

@@ -142,11 +142,6 @@ To reduce the available tools, you can pass an allow-list in two ways:
142142

143143
The environment variable `GITHUB_TOOLSETS` takes precedence over the command line argument if both are provided.
144144

145-
Any toolsets you specify will be enabled from the start, including when `--dynamic-toolsets` is on.
146-
147-
You might want to do this if the model is confused about which tools to call and you only require a subset.
148-
149-
150145
### Using Toolsets With Docker
151146

152147
When using Docker, you can pass the toolsets as environment variables:
@@ -174,9 +169,9 @@ GITHUB_TOOLSETS="all" ./github-mcp-server
174169

175170
## Dynamic Tool Discovery
176171

177-
Instead of starting with all tools enabled, you can turn on Dynamic Toolset Discovery.
178-
This feature provides tools that help the MCP Host application to discover and enable sets of GitHub tools only when needed.
179-
This helps to avoid situations where models get confused by the shear number of tools available to them, which varies by model.
172+
**Note**: This feature is currently in beta and may not be available in all environments. Please test it out and let us know if you encounter any issues.
173+
174+
Instead of starting with all tools enabled, you can turn on dynamic toolset discovery. Dynamic toolsets allow the MCP host to list and enable toolsets in response to a user prompt. This should help to avoid situations where the model gets confused by the shear number of tools available.
180175

181176
### Using Dynamic Tool Discovery
182177

@@ -195,8 +190,6 @@ docker run -i --rm \
195190
ghcr.io/github/github-mcp-server
196191
```
197192

198-
199-
200193
## GitHub Enterprise Server
201194

202195
The flag `--gh-host` and the environment variable `GH_HOST` can be used to set

0 commit comments

Comments
 (0)