How can a server using the SSE (Server-Sent Events) model over HTTP support additional content like images within the conversational context?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the ConvertImageFormat tool call over the SSE and HTTP setup described in the issue, then inspect how the server handles image content in the conversational context. Done means the tool call succeeds and images can be supported alongside the conversation; no source files or tests are identified in the report.
Written by the indexing model from the issue text.
Description
[McpServerTool(Name = "ConvertImageFormat")]
[Description("Converts image format")]
public static async Task<string> ConvertImageFormat(
[Description("Base64 encoded image data")] string imageData,
[Description("Target format: jpeg, png, bmp")] string targetFormat)
{
try
{
if (imageData.Contains(","))
{
imageData = imageData.Split(',')[1];
}
byte[] imageBytes = Convert.FromBase64String(imageData);
// Here you can integrate System.Drawing or ImageSharp for format conversion
// For simplicity, this is just simulating the conversion
var convertedBytes = await SimulateImageConversion(imageBytes, targetFormat);
var convertedBase64 = Convert.ToBase64String(convertedBytes);
return $"Image format conversion completed:\n" +
$"- Original size: {imageBytes.Length} bytes\n" +
$"- Converted size: {convertedBytes.Length} bytes\n" +
$"- Target format: {targetFormat}\n" +
$"- Converted base64 data: data:image/{targetFormat};base64,{convertedBase64}";
}
catch (Exception ex)
{
return $"Error: Failed to convert image format - {ex.Message}";
}
}
This approach/way of writing does not successfully call it.
- Dominant language
- C#
- Stars
- 4.5k
- Forks
- 814
- Avg merge
- 9d 19h
- Merged PRs (30d)
- 4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/csharp-sdk
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/csharp-sdk#1867 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
modelcontextprotocol/csharp-sdk#1840 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
modelcontextprotocol/csharp-sdk#1836 ·
-
enhancement needs confirmation
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
modelcontextprotocol/csharp-sdk#678 · 1 comment ·
-
enhancement needs confirmation P3 ready for work
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/csharp-sdk#515 · 6 comments · 3 reactions ·
All issues in modelcontextprotocol/csharp-sdk
Similar issues
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·
-
.NET Flaky Test Testing Tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-dotnet#5617 · 1 comment ·
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·