build1 publisher
Keeping one tool description in two files forked this MCP contract in two days
In a dev.to sample the same restaurant search tool is described once in a C# attribute and twice in Bicep, and two of the copies already disagree after two days of editing. The author's argument is that the description is the API contract now.
Publishers:dev.to
Reality
- Evidence45
- Adoption12
- Hype gap+12
- Incentives38
- Confidence52