fix: fix rig chat agent output format

[Akagi201]

Motivation and Context

Fix rig-integration example agent response format.

Before fix

MCP Manager created, 1 servers started
get tool: git_status
get tool: git_diff_unstaged
get tool: git_diff_staged
get tool: git_diff
get tool: git_commit
get tool: git_add
get tool: git_reset
get tool: git_log
get tool: git_create_branch
get tool: git_checkout
get tool: git_show
Enter :q to quit
user> show me the status of git repo
🤖 Agent: 🤖 Agent:
🤖 Agent: To
🤖 Agent:  check
🤖 Agent:  the
🤖 Agent:  status
🤖 Agent:  of
🤖 Agent:  a
🤖 Agent:  Git
🤖 Agent:  repository
🤖 Agent: ,
🤖 Agent:  the
🤖 Agent:  appropriate
🤖 Agent:  tool
🤖 Agent:  would
🤖 Agent:  be
🤖 Agent:  one
🤖 Agent:  that
🤖 Agent:  can
🤖 Agent:  execute
🤖 Agent:  Git
🤖 Agent:  commands
🤖 Agent: .
🤖 Agent:  Based
🤖 Agent:  on
🤖 Agent:  the
🤖 Agent:  instructions
🤖 Agent:  provided
🤖 Agent: ,
🤖 Agent:  I
🤖 Agent:  would
🤖 Agent:  need
🤖 Agent:  to
🤖 Agent:  use
🤖 Agent:  a
🤖 Agent:  tool
🤖 Agent:  that
🤖 Agent:  can
🤖 Agent:  interact
🤖 Agent:  with
🤖 Agent:  the
🤖 Agent:  Git
🤖 Agent:  system
🤖 Agent: .


🤖 Agent: Tool
🤖 Agent: :
🤖 Agent:  git
🤖 Agent: _status
🤖 Agent:

🤖 Agent: Input
🤖 Agent: s
🤖 Agent: :
🤖 Agent:  None
🤖 Agent:  (
🤖 Agent: since
🤖 Agent:  "
🤖 Agent: git
🤖 Agent:  status
🤖 Agent: "
🤖 Agent:  doesn
🤖 Agent: 't
🤖 Agent:  typically
🤖 Agent:  require
🤖 Agent:  additional
🤖 Agent:  inputs
🤖 Agent:  beyond
🤖 Agent:  the
🤖 Agent:  repository
🤖 Agent:  context
🤖 Agent: )
🤖 Agent:
user>

After fixed

MCP Manager created, 1 servers started
get tool: git_status
get tool: git_diff_unstaged
get tool: git_diff_staged
get tool: git_diff
get tool: git_commit
get tool: git_add
get tool: git_reset
get tool: git_log
get tool: git_create_branch
get tool: git_checkout
get tool: git_show
Enter :q to quit
user> show me the status of git repo
🤖 Agent: To check the status of a Git repository, we would typically use the `git status` command. Based on the instructions provided, I should select the appropriate tool for this task rather than performing it directly.

Tool: git_status
Inputs: []

(Note: Since `git status` doesn't typically require additional inputs when checking the basic status, the inputs list is empty. If you need to check the status of a specific path or with specific options, those would be included as inputs.)
user>

How Has This Been Tested?

Yes

Breaking Changes

No

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

Additional context

[jokemanfire]

Thanks