Disappearance of `ToolFor`

[slacaze]

Hi,

In #517, I mentioned I depend on a workflow where I can override the tool definition.

I suppose I should have been for explicit, and mentioned I was using:

toolDefinition, typeLessHandler := mcp.ToolFor

To make an initialization, and wrapping the handler, and then calling sever.AddTool.

However ToolFor seems to have disappeared, leaving me with no way to get the wrapped Handler. Without it, server.AddTool (as opposed to mcp.AddTool) seems quite hard to use and get right.

Specifically, the case I'm struggling to ensure I can replicate is the case where OutputSchema was inferred to something, but I want to set it to nil.

It was trivial with ToolFor, but I don't think I can anymore, because if I call mcp.AddTool, specify OutputSchema to nil, and pass a Handler whose OutputType is not nil, it will add an inferred OutputSchema.

[jba]

Why do you want to set the OutputSchema to nil? Can you use an output type of any to get the same effect?

[slacaze]

Initially, I was struggling to integrate the use of generics in this project into our framework, and so I worked around it, allowing me to have handlers with a return type, that converted to unstructured content. Ultimately, we have mostly structured content handlers, but we have a few that wan to return images, and as far as I can tell from the spec, you can't do that with structured content (i.e., you can't have field of type ImageContent or whatever).

But I think I found a way in the end.

[jba]

Can you describe it for others who come down this same path?
Also see #396 (comment).
Specifically, AddUnstructuredTool.

[slacaze]

Thanks, done.

It was a good link, because the 2 proposed AddXTool are what I ended up making on my side.