Different LLMs can behave differently when given the same tool definition.
A tool description and input schema that work well with one model may perform worse with another. One model may select the right tool and arguments, while another may select the wrong tool or generate invalid arguments from the same definition.
WebMCP could support model-aware tool definitions.
description: ({ model, modelFamily }) => {
if (model === "gpt-5.6") {
return "...";
}
if (modelFamily === "gpt-5") {
return "...";
}
return "Search for products.";
},The exact API is just an example. Developers could return different tool descriptions, schemas, or parameter descriptions based on the model or model family, with a default fallback.
P.S. This is my first contribution to WebMCP!
Different LLMs can behave differently when given the same tool definition.
A tool description and input schema that work well with one model may perform worse with another. One model may select the right tool and arguments, while another may select the wrong tool or generate invalid arguments from the same definition.
WebMCP could support model-aware tool definitions.
The exact API is just an example. Developers could return different tool descriptions, schemas, or parameter descriptions based on the model or model family, with a default fallback.
P.S. This is my first contribution to WebMCP!