feat(mcp): Add list_prompts, get_prompt methods

[Ketansuhaas]

Description

This PR introduces two new methods to the MCPClient class: list_prompts_sync and get_prompt_sync.

• list_prompts_sync: This method synchronously retrieves a list of available prompts from the MCP server. It calls the asynchronous list_prompts method on the underlying MCP session and returns the ListPromptsResult.
• get_prompt_sync: This method synchronously retrieves a specific prompt by its ID from the MCP server, along with any specified arguments. It calls the asynchronous get_prompt method on the MCP session and returns the GetPromptResult.

These additions enhance the MCPClient's capabilities to interact with MCP-based prompt services.

How to use:

Listing available prompts:

# Assuming mcp_client is an initialized MCPClient instance
prompts_result = mcp_client.list_prompts_sync()
for prompt in prompts_result.prompts:
    print(f"Prompt Name: {prompt.name}")
    print(f"Prompt Arguments: {prompt.arguments}")
    # print(f"Prompt Description: {prompt.description}") # If available

Getting a specific prompt:

# Assuming mcp_client is an initialized MCPClient instance
prompt_id_to_get = "sum-two-numbers" # Example prompt ID
arguments_for_prompt = {
    "a": "123",
    "b": "456"
}
prompt_response = mcp_client.get_prompt_sync(prompt_id_to_get, arguments_for_prompt)
if prompt_response.messages:
    print(f"Prompt Content: {prompt_response.messages[0].content.text}")

Related Issues

N/A

Documentation PR

N/A

Type of Change

• New feature

Testing

• hatch fmt --linter
• hatch fmt --formatter
• hatch test --all
• Verify that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli

Checklist

• I have read the CONTRIBUTING document
• I have added tests that prove my fix is effective or my feature works
• I have updated the documentation accordingly
• I have added an appropriate example to the documentation to outline the feature
• My changes generate no new warnings
• Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[awsarron]

related: #151

[dbschmigelski]

Hi,

Sorry but this has increased in priority because of internal needs. Thanks for marking this as editable by maintainers. I am taking over the PR to rebase, make some edits, and add tests. But @Ketansuhaas you will still have attribution on the PR, thanks for raising this.

[Ketansuhaas]

Hi,

Sorry but this has increased in priority because of internal needs. Thanks for marking this as editable by maintainers. I am taking over the PR to rebase, make some edits, and add tests. But @Ketansuhaas you will still have attribution on the PR, thanks for raising this.

Thank you. I appreciate it.

[dbschmigelski]

Noting that the recommendation in this PR is to expose the raw MCP SDK responses. This was not done for tools as the benefit of the MCPClient was to map the MCP tool to a Strands AgentTool.

For Prompts and Resources, there is not native Strand concept. So we have two options one is to expose them with 1-1 methods as we have here. The other is to instruct users to use the underlying mcp session that is created. I agree with the initial proposal that interacting with MCPClient(strands) and the underling MCPClient.session seems strange. Additionally, allowing users to operate in both sync and async mode requires us to handle the wrapping ourselves as the underlying method is async.

dismissing as I was the one who made many of these changes and should not self-review.