Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
menix
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
by
menix
7mo ago
One aspect I think is often overlooked in the CLI vs. MCP debate: MCP's support for structured output and output schema (introduced in the 2025-06-18 spec). This is a genuinely underrated feature that has practical implications far bey
2.
▲
by
menix
10mo ago
smolagents by Hugging Face tackles your issues with MCP tools. They added support for the output schema and structured output provided by the latest MCP spec. This way print and inspect is no longer necessary. https://huggingfac
3.
▲
by
menix
10mo ago
The latest MCP specifications (2025-06-18+) introduced crucial enhancements like support for Structured Content and the Output Schema. Smolagents makes use of this and handles tool output as objects (e.g. dict). Is this what you are thinkin
4.
▲
by
menix
10mo ago
Wrapping tool calls in code together with using the benefits of the MCP output schema was implemented in smolagents for some time. Think that’s even one step further conceptually. https://huggingface.co/blog/llchahn&#x
5.
▲
by
menix
1y ago
smolagents provides something very similar: https://huggingface.co/blog/llchahn/ai-agents-output-schema
6.
▲
Output Schema for CodeAct AI Agents: From Trial-and-Error to Predictive Planning
(huggingface.co)
3 points
by
menix
1y ago
|
1 comments
7.
▲
by
menix
1y ago
The latest Model Context Protocol introduces Output Schema: agents now know the exact data structure a tool will return before calling it. This eliminates the "print-and-inspect" pattern where CodeAct agents call tools just to dis
8.
▲
by
menix
8y ago
For me magnesium (oral) works very well. 100mg to 300mg per day. Decreased my migraine from weekly to once per half year.
9.
▲
by
menix
10y ago
Mark Gurman even mentioned a lot of good people were leaving the company. ( https://www.bloomberg.com/news/articles/2016-12-20/how-apple... )