-
Notifications
You must be signed in to change notification settings - Fork 299
add (docs): add some newer fields to the gpt file reference #683
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
iwilltry42
merged 3 commits into
gptscript-ai:main
from
iwilltry42:chore/docs-gptscript-reference
Aug 1, 2024
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,21 +43,25 @@ Tool instructions go here. | |
|
||
Tool parameters are key-value pairs defined at the beginning of a tool block, before any instructional text. They are specified in the format `key: value`. The parser recognizes the following keys (case-insensitive and spaces are ignored): | ||
|
||
| Key | Description | | ||
|--------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| | ||
| `Name` | The name of the tool. | | ||
| `Model Name` | The LLM model to use, by default it uses "gpt-4-turbo". | | ||
| `Global Model Name`| The LLM model to use for all the tools. | | ||
| `Description` | The description of the tool. It is important that this properly describes the tool's purpose as the description is used by the LLM. | | ||
| `Internal Prompt` | Setting this to `false` will disable the built-in system prompt for this tool. | | ||
| `Tools` | A comma-separated list of tools that are available to be called by this tool. | | ||
| `Global Tools` | A comma-separated list of tools that are available to be called by all tools. | | ||
| `Credentials` | A comma-separated list of credential tools to run before the main tool. | | ||
| `Args` | Arguments for the tool. Each argument is defined in the format `arg-name: description`. | | ||
| `Max Tokens` | Set to a number if you wish to limit the maximum number of tokens that can be generated by the LLM. | | ||
| `JSON Response` | Setting to `true` will cause the LLM to respond in a JSON format. If you set true you must also include instructions in the tool. | | ||
| `Temperature` | A floating-point number representing the temperature parameter. By default, the temperature is 0. Set to a higher number for more creativity. | | ||
| `Chat` | Setting it to `true` will enable an interactive chat session for the tool. | | ||
| Key | Description | | ||
|----------------------|-----------------------------------------------------------------------------------------------------------------------------------------------| | ||
| `Name` | The name of the tool. | | ||
| `Model Name` | The LLM model to use, by default it uses "gpt-4-turbo". | | ||
| `Global Model Name` | The LLM model to use for all the tools. | | ||
| `Description` | The description of the tool. It is important that this properly describes the tool's purpose as the description is used by the LLM. | | ||
| `Internal Prompt` | Setting this to `false` will disable the built-in system prompt for this tool. | | ||
| `Tools` | A comma-separated list of tools that are available to be called by this tool. | | ||
| `Global Tools` | A comma-separated list of tools that are available to be called by all tools. | | ||
| `Parameter` / `Args` | Arguments for the tool. Each argument is defined in the format `arg-name: description`. | | ||
| `Max Tokens` | Set to a number if you wish to limit the maximum number of tokens that can be generated by the LLM. | | ||
| `JSON Response` | Setting to `true` will cause the LLM to respond in a JSON format. If you set true you must also include instructions in the tool. | | ||
| `Temperature` | A floating-point number representing the temperature parameter. By default, the temperature is 0. Set to a higher number for more creativity. | | ||
| `Chat` | Setting it to `true` will enable an interactive chat session for the tool. | | ||
| `Credential` | Credential tool to call to set credentials as environment variables before doing anything else. One per line. | | ||
| `Agents` | A comma-separated list of agents that are available to the tool. | | ||
| `Share Tools` | A comma-separated list of tools that are shared by the tool. | | ||
| `Context` | A comma-separated list of context tools available to the tool. | | ||
| `Share Context` | A comma-separated list of context tools shared by this tool with any tool including this tool in its context. | | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There's more here, but I'm not sure if we should put everything (e.g. temperature and max_tokens) here |
||
|
||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only for consistency within this page
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm probably going to go through and capitalize everything (I think that's the more canonical way now) as I work on my docs revamp, so this is fine either way for now.