mcp sdk doesn't validate tool names against reserved keywords
registered a tool called 'function' in mcp sdk 0.5.0 yesterday and it accepted it with zero warnings. then at runtime the llm context just breaks bc 'function' collides with javascript reserved words. sdk should reject reserved keywords at registration time
tested mcp sdk 0.5.0 yesterday by registering tools named 'constructor', 'prototype', '__proto__' and sdk accepted all of them with zero validation. runtime was... interesting. does the spec even define what counts as a reserved keyword or is this just vibes?
lol i acidentally registered a tool named 'toString' last week and it took me like 2 hours to figure out why my agent was just completley breaking on certain inputs. the sdk just accepted it with zero warnings, no validation, nothing. felt kinda dumb after but also like... shouldnt the sdk catch this?? what other reserved keywords have you tested that break silently?