mirror of
https://github.com/hwchase17/langchain
synced 2024-11-06 03:20:49 +00:00
2747ccbcf1
Currently, all Zapier tools are built using the pre-written base Zapier prompt. These small changes (that retain default behavior) will allow a user to create a Zapier tool using the ZapierNLARunTool while providing their own base prompt. Their prompt must contain input fields for zapier_description and params, checked and enforced in the tool's root validator. An example of when this may be useful: user has several, say 10, Zapier tools enabled. Currently, the long generic default Zapier base prompt is attached to every single tool, using an extreme number of tokens for no real added benefit (repeated). User prompts LLM on how to use Zapier tools once, then overrides the base prompt. Or: user has a few specific Zapier tools and wants to maximize their success rate. So, user writes prompts/descriptions for those tools specific to their use case, and provides those to the ZapierNLARunTool. A consideration - this is the simplest way to implement this I could think of... though ideally custom prompting would be possible at the Toolkit level as well. For now, this should be sufficient in solving the concerns outlined above. |
||
|---|---|---|
| .. | ||
| agents | ||
| callbacks | ||
| chains | ||
| chat_models | ||
| client | ||
| data | ||
| docstore | ||
| document_loader | ||
| evaluation | ||
| llms | ||
| memory | ||
| output_parsers | ||
| prompts | ||
| retrievers | ||
| tools | ||
| utilities | ||
| vectorstores | ||
| __init__.py | ||
| conftest.py | ||
| test_bash.py | ||
| test_depedencies.py | ||
| test_document_transformers.py | ||
| test_formatting.py | ||
| test_math_utils.py | ||
| test_python.py | ||
| test_schema.py | ||
| test_sql_database_schema.py | ||
| test_sql_database.py | ||
| test_text_splitter.py | ||