vlaaad (u/vlaaad) - Readit News

vlaaad commented on Angry Metal Guy Speaks: On Spotify angrymetalguy.com/angry-m... · Posted by u/nixass

dmonitor · 4 days ago

Using AI generated art in a blog post where one of the major points is big companies using AI art to replace artists is ironic.

vlaaad · 4 days ago

Yes, though I also liked the overall point of the post. Spotify recommendations are shit, and any playlist made by Spotify is full of garbage. I guess Ek knows this and, perhaps unconsciously, sees himself as evil, doing what's legal no matter how bad it is, with his weapon investments...

vlaaad commented on MCP tools with dependent types vlaaad.github.io/mcp-tool... · Posted by u/vlaaad

WithinReason · 11 days ago

And LLMs will get more accurate. What happens when the LLM uses the wrong parameters? If it's an immediate error then it will just try again, no need for protocol changes, just better LLMs.

vlaaad · 11 days ago

The difference between 99% reliability and 100% reliability is huge in this case.

vlaaad commented on MCP tools with dependent types vlaaad.github.io/mcp-tool... · Posted by u/vlaaad

nmilo · 11 days ago

I don't think this is a protocol issue, the LLMs simply weren't RLHFed to do that

vlaaad · 11 days ago

Not true, structured outputs enforce output formats with 100% reliability, e.g., https://platform.openai.com/docs/guides/structured-outputs says "Structured Outputs is a feature that ensures the model will always generate responses that adhere to your supplied JSON Schema, so you don't need to worry about the model omitting a required key, or hallucinating an invalid enum value"

vlaaad commented on MCP tools with dependent types vlaaad.github.io/mcp-tool... · Posted by u/vlaaad

LudwigNagasena · 11 days ago

> there is no way to tell the AI agent “for this argument, look up a JSON schema using this other tool”

There is a description field, it seems sufficient for most cases. You can also dynamically change your tools using `listChanged` capability.

vlaaad · 11 days ago

Sure, but the need for accuracy will only increase; there is a difference between suggesting an LLM to put a schema in its context before calling the tool vs forcing the LLM to use a structured output returned from a tool dynamically.

We already have 100% reliable structured outputs if we are making chatbots with LLM integrations directly; I don't want to lose this.

vlaaad commented on MCP tools with dependent types vlaaad.github.io/mcp-tool... · Posted by u/vlaaad

vlaaad · 11 days ago

I was considering making an MCP SEP (specification enhancement proposal) — https://modelcontextprotocol.io/community/sep-guidelines, though I'm curious if other MCP tinkerers feel the issue exists, should be solved like that, etc. What do you think?

Posted by u/vlaaad 11 days ago

MCP tools with dependent types vlaaad.github.io/mcp-tool...

vlaaad commented on MCP Tools with Dependent Types vlaaad.github.io/mcp-tool... · Posted by u/vlaaad

VivaTechnics · 12 days ago

Good work! `type<T>` (generic types) can mimic dependent types for this?

vlaaad · 12 days ago

Not sure; the schema of the Props argument depends on the value — not type — of another argument, so it's not just generics.

Posted by u/vlaaad 12 days ago

MCP Tools with Dependent Types vlaaad.github.io/mcp-tool...

Posted by u/vlaaad 16 days ago

Building ad-hoc analytics in Clojure with Reveal vlaaad.github.io/ad-hoc-a...

Posted by u/vlaaad 17 days ago

I built ad-hoc analytics service with Reveal vlaaad.github.io/ad-hoc-a...

u/vlaaad

KarmaCake day689July 31, 2014View Original