1 00:00:00,140 --> 00:00:05,200 Have you ever spent hours, like, writing this incredibly detailed SQL schema or 2 00:00:05,340 --> 00:00:09,700 OpenAPI spec for an MCP tool, only to feel like Claude is just, 3 00:00:10,040 --> 00:00:12,760 uh, completely ignoring half your instructions? 4 00:00:12,973 --> 00:00:14,193 Oh, man, constantly! 5 00:00:14,793 --> 00:00:18,773 You think it's a prompt engineering issue, or maybe the model's just hallucinating, 6 00:00:18,853 --> 00:00:20,033 but it turns out... 7 00:00:20,633 --> 00:00:24,473 it was actually getting chopped off at TWO THOUSAND FORTY EIGHT characters! 8 00:00:24,982 --> 00:00:26,062 Exactly right, mate! 9 00:00:26,502 --> 00:00:28,202 Pure, silent truncation. 10 00:00:28,942 --> 00:00:32,142 But in Claude Code version two point one point two hundred and eighty, 11 00:00:32,642 --> 00:00:34,842 Anthropic finally gave us an escape hatch. 12 00:00:35,582 --> 00:00:40,601 And hey, quick shoutout to our sponsor Jellypod AI, making podcast creation as 13 00:00:40,662 --> 00:00:41,882 smooth as clean code. 14 00:00:42,177 --> 00:00:44,937 Yeah, so what is this escape hatch actually called? 15 00:00:45,118 --> 00:00:49,938 It's an environment variable: CLAUDE CODE MAX MCP DESCRIPTION LENGTH. 16 00:00:50,160 --> 00:00:51,780 Say that three times fast! 17 00:00:52,320 --> 00:00:56,620 But wait, so by default, every tool description and server instruction in Model 18 00:00:56,720 --> 00:01:00,620 Context Protocol had a hard two thousand forty eight character cap? 19 00:01:00,750 --> 00:01:02,750 Yeah, two thousand forty eight characters. 20 00:01:02,963 --> 00:01:07,790 If your database schema or, or tool documentation went over that limit, 21 00:01:07,817 --> 00:01:08,750 it just got clipped. 22 00:01:08,910 --> 00:01:11,630 No warning, no error message, just gone. 23 00:01:11,907 --> 00:01:13,767 That's brutal for enterprise tools. 24 00:01:14,147 --> 00:01:18,347 I mean, if you're wrapping a massive API with dozens of parameters, 25 00:01:18,827 --> 00:01:20,987 two thousand characters disappears instantly. 26 00:01:21,042 --> 00:01:21,762 Spot on. 27 00:01:21,815 --> 00:01:25,122 So now, you can just export that environment variable in your terminal. 28 00:01:25,262 --> 00:01:28,642 Say, setting it to eight thousand one hundred and ninety two. 29 00:01:28,667 --> 00:01:35,387 Okay, so if I run export CLAUDE CODE MAX MCP DESCRIPTION LENGTH equals eight 30 00:01:35,431 --> 00:01:40,267 thousand one hundred and ninety two, boom, my entire schema fits into context! 31 00:01:40,472 --> 00:01:40,952 Bang on. 32 00:01:41,512 --> 00:01:44,632 But, uh, you know, there's a flip side to cranking that all the way up. 33 00:01:45,365 --> 00:01:50,045 Right, because every single turn, those expanded tool descriptions get stuffed right 34 00:01:50,105 --> 00:01:51,565 into your input prompt, don't they? 35 00:01:51,625 --> 00:01:52,505 Exactly, mate. 36 00:01:52,605 --> 00:01:55,385 You're paying for those input tokens on every turn. 37 00:01:55,529 --> 00:02:00,105 Plus, if you keep changing tool descriptions on the fly, you invalidate your prompt 38 00:02:00,185 --> 00:02:00,905 cache! 39 00:02:00,917 --> 00:02:01,717 Oof, yeah. 40 00:02:01,749 --> 00:02:04,357 That cache miss fee will bite you real quick. 41 00:02:04,457 --> 00:02:08,357 And honestly, if you make descriptions too wordy, the model can actually get 42 00:02:08,419 --> 00:02:10,197 confused about which tool to pick. 43 00:02:10,208 --> 00:02:13,808 Yeah, too much noise in the description degrades tool routing accuracy. 44 00:02:13,995 --> 00:02:15,608 So it's a balance. 45 00:02:15,718 --> 00:02:19,408 You can even dial it down to, say, five hundred twelve characters for lightweight 46 00:02:19,461 --> 00:02:23,008 wrappers if you want to shave down your input context overhead. 47 00:02:23,042 --> 00:02:24,162 Oh, that's smart! 48 00:02:24,282 --> 00:02:28,962 And you can monitor your prompt token usage right in the CLI by typing slash status, 49 00:02:28,989 --> 00:02:29,282 right? 50 00:02:29,432 --> 00:02:30,652 Slash status, yeah! 51 00:02:31,212 --> 00:02:32,892 Shows you your context usage right there. 52 00:02:33,000 --> 00:02:34,760 Man, that's such a solid tweak. 53 00:02:34,900 --> 00:02:39,160 And speaking of CLI fixes in two point one point two hundred and eighty, 54 00:02:39,200 --> 00:02:40,600 did you see the Write tool patch? 55 00:02:40,965 --> 00:02:43,425 Oh, mate, I hit that bug last week! 56 00:02:44,125 --> 00:02:49,325 Models kept passing path or file text instead of file path and content, 57 00:02:49,725 --> 00:02:52,565 and the validator would just throw a wobbly and crash the call. 58 00:02:52,625 --> 00:02:53,025 Right! 59 00:02:53,085 --> 00:02:55,505 Now it handles parameter aliases gracefully. 60 00:02:55,638 --> 00:02:59,265 So if the model sends file content or a stray description field, 61 00:02:59,311 --> 00:03:02,305 Claude Code normalizes it instead of failing validation. 62 00:03:02,333 --> 00:03:03,133 Such a relief. 63 00:03:03,426 --> 00:03:09,453 Oh, and double pressing Control C or Control D inside modals like slash model or 64 00:03:09,520 --> 00:03:14,573 slash config actually closes the dialog now, instead of nuking your whole terminal 65 00:03:14,623 --> 00:03:15,293 session! 66 00:03:16,113 --> 00:03:16,893 Thank goodness! 67 00:03:17,453 --> 00:03:20,873 I lost count of how many active sessions I accidentally killed trying to exit a 68 00:03:20,913 --> 00:03:21,253 menu! 69 00:03:21,893 --> 00:03:26,373 Plus, mouse wheel scrolling finally works in slash skills and slash plugin in 70 00:03:26,393 --> 00:03:27,153 fullscreen mode. 71 00:03:27,208 --> 00:03:30,888 Simple stuff, but it makes the whole developer experience so much smoother. 72 00:03:30,997 --> 00:03:31,477 Definitely. 73 00:03:31,617 --> 00:03:36,297 Definitely update to two point one point two hundred and eighty if you're heavy on 74 00:03:36,377 --> 00:03:37,337 MCP tools. 75 00:03:38,037 --> 00:03:38,797 Alright, good chatting! 76 00:03:38,875 --> 00:03:40,235 Good chatting, talk soon!