Skip to content
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

core[minor]: Allow for simple tool schema to be passed to bindTools #8

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

korbit-ai[bot]
Copy link

@korbit-ai korbit-ai bot commented Aug 15, 2024

Allows for a more concise schema to be passed to models. This is not intended to be used in Agents or similar since it has no function attached, and is more similar to .withStructuredOutput.

TODO:

  • after releasing, bump min core version for all.

Description by Korbit AI

Note

This feature is in early access. You can enable or disable it in the Korbit Console.

What change is being made?

Add support for passing a simple tool schema to the bindTools method by introducing the ToolSchema interface and updating the BaseChatModel class to accept ToolSchema as a valid input type.

Why are these changes being made?

This change enhances the flexibility of the bindTools method, allowing developers to define and pass tool schemas more easily, which simplifies the integration of tools with the chat model. This approach provides a more structured and descriptive way to handle tool parameters.

Summary by CodeRabbit

  • New Features

    • Introduced ToolSchema to enhance tool management within the chat model, allowing for more complex interactions and integrations.
    • Updated the BaseChatModel to accept a broader range of message data structures, improving flexibility for developers.
  • Improvements

    • Enhanced type safety and clarity for tool definitions by adding a structured ToolSchema interface.

Copy link
Author

korbit-ai bot commented Aug 15, 2024

Clone of the PR langchain-ai/langchainjs#6253

Copy link
Author

korbit-ai bot commented Aug 15, 2024

My review is in progress 📖 - I will have feedback for you in a few minutes!

Copy link

coderabbitai bot commented Aug 15, 2024

Walkthrough

The recent updates introduce significant improvements to the LangChain framework by enhancing the BaseChatModel class and introducing the ToolSchema interface. These changes expand the types of data that can be utilized in chat interactions, promoting greater flexibility and robustness in tool integration. Developers can now better define and validate tools, leading to more sophisticated functionalities within applications.

Changes

Files Change Summary
langchain-core/src/language_models/chat_models.ts, langchain-core/src/tools/index.ts Enhanced BaseChatModel to accept ToolSchema in the messages parameter. Introduced the ToolSchema interface to structure tool-related data, improving type safety and clarity.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ChatModel
    participant Tool

    User->>ChatModel: Send message
    ChatModel->>Tool: Validate and process ToolSchema
    Tool-->>ChatModel: Return processed data
    ChatModel-->>User: Respond with message
Loading

Poem

🐰 In the meadow where tools do play,
A schema blooms, brightening the day.
With messages flowing, interactions sweet,
We hop towards features, oh what a treat!
So let’s dance and sing, for code is our art,
With each little change, we grow smart! 🌼✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Author

@korbit-ai korbit-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have reviewed your code and found 2 potential issues.

@@ -33,7 +33,7 @@ import {
} from "../callbacks/manager.js";
import type { RunnableConfig } from "../runnables/config.js";
import type { BaseCache } from "../caches/base.js";
import { StructuredToolInterface } from "../tools/index.js";
import { StructuredToolInterface, ToolSchema } from "../tools/index.js";
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

category Readability and Maintainability

The import statement for ToolSchema is added but not used anywhere in the file. Unused imports can clutter the code and make it harder to read and maintain. Please remove the unused import statement for ToolSchema to keep the code clean and maintainable.

Chat with Korbit by mentioning @korbit-ai, and give a 👍 or 👎 to help Korbit improve your reviews.

Comment on lines +50 to +63
export interface ToolSchema {
/**
* The name of the tool to pass to the model.
*/
name: string;
/**
* An optional description of the tool to pass to the model.
*/
description?: string;
/**
* A Zod schema representing the parameters of the tool.
*/
schema: ZodObjectAny;
}
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

category Functionality

The new ToolSchema interface has been added, which is a good addition for allowing more concise schema definitions. However, to ensure proper functionality and prevent misuse, we should add comments explaining its intended use and limitations. Specifically, we should note that this is not intended to be used in Agents or similar contexts, as it has no function attached. Consider adding a comment above the ToolSchema interface to clarify its purpose and usage constraints.

Chat with Korbit by mentioning @korbit-ai, and give a 👍 or 👎 to help Korbit improve your reviews.

@furwellness
Copy link
Owner

/review

Copy link

codiumai-pr-agent-free bot commented Aug 16, 2024

PR Reviewer Guide 🔍

(Review updated until commit d7a0236)

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪
🧪 No relevant tests
🔒 No security concerns identified
⚡ Key issues to review

Type Definition Update
The bindTools method's parameter type has been expanded to include ToolSchema. This change should be reviewed to ensure it doesn't break existing functionality and is properly implemented throughout the codebase.

New Interface
A new ToolSchema interface has been introduced. This should be reviewed for completeness and correctness, ensuring it meets the intended use cases and doesn't conflict with existing interfaces.

@furwellness furwellness reopened this Aug 20, 2024
@furwellness furwellness changed the base branch from cloned_main_12963 to main August 20, 2024 23:49
Copy link

Persistent review updated to latest commit d7a0236

@furwellness
Copy link
Owner

@coderabbitai full review

Copy link

coderabbitai bot commented Aug 20, 2024

Actions performed

Full review triggered.

Copy link

PR Code Suggestions ✨

CategorySuggestion                                                                                                                                    Score
Enhancement
Improve type definition by using a union type instead of an array for better type safety and readability

Consider using a union type instead of an array for the tools parameter. This would
provide better type safety and make the code more readable.

langchain-core/src/language_models/chat_models.ts [184-188]

 | Record<string, unknown>
 | ToolDefinition
 | RunnableToolLike
-+| ToolSchema
-)[],
+| ToolSchema
 
  • Apply this suggestion
Suggestion importance[1-10]: 7

Why:

7
Add a 'required' property to the ToolSchema interface to specify which parameters are mandatory

Consider adding a required property to the ToolSchema interface to specify which
parameters are required. This would provide more information to the model about the
tool's usage.

langchain-core/src/tools/index.ts [50-63]

 export interface ToolSchema {
   /**
    * The name of the tool to pass to the model.
    */
   name: string;
   /**
    * An optional description of the tool to pass to the model.
    */
   description?: string;
   /**
    * A Zod schema representing the parameters of the tool.
    */
   schema: ZodObjectAny;
+  /**
+   * An array of required parameter names.
+   */
+  required?: string[];
 }
 
  • Apply this suggestion
Suggestion importance[1-10]: 7

Why:

7
Best practice
Rename the 'schema' property to 'parameters' in the ToolSchema interface for better consistency and clarity

Consider adding a parameters property to the ToolSchema interface instead of using
schema. This would make it more consistent with OpenAI's function calling format and
improve clarity.

langchain-core/src/tools/index.ts [50-63]

 export interface ToolSchema {
   /**
    * The name of the tool to pass to the model.
    */
   name: string;
   /**
    * An optional description of the tool to pass to the model.
    */
   description?: string;
   /**
-   * A Zod schema representing the parameters of the tool.
+   * An object representing the parameters of the tool.
    */
-  schema: ZodObjectAny;
+  parameters: ZodObjectAny;
 }
 
  • Apply this suggestion
Suggestion importance[1-10]: 7

Why:

7

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range, codebase verification and nitpick comments (1)
langchain-core/src/tools/index.ts (1)

50-63: Add documentation for ToolSchema usage.

The ToolSchema interface is a valuable addition for defining concise tool schemas. However, to ensure proper usage and prevent misuse, add comments explaining its intended use and limitations. Specifically, note that it is not intended for use in Agents or similar contexts, as it lacks an attached function.

+/**
+ * Interface for defining concise tool schemas.
+ * Note: This is not intended for use in Agents or similar contexts, as it lacks an attached function.
+ */
export interface ToolSchema {
  name: string;
  description?: string;
  schema: ZodObjectAny;
}
Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9db8299 and d7a0236.

Files selected for processing (2)
  • langchain-core/src/language_models/chat_models.ts (2 hunks)
  • langchain-core/src/tools/index.ts (1 hunks)
Additional comments not posted (1)
langchain-core/src/language_models/chat_models.ts (1)

36-36: Remove unused import of ToolSchema.

The import statement for ToolSchema is added but not used anywhere in the file. Unused imports can clutter the code and make it harder to read and maintain. Please remove the unused import statement for ToolSchema to keep the code clean and maintainable.

@furwellness
Copy link
Owner

Zero comments from coderabbit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants