Almog
banner
almog.xyz
Almog
@almog.xyz
Favorite Buzzwords: Kafka Streams | SlateDB | Stream Processing | Distributed Databases

co-founder @ https://responsive.dev
I wonder why it hasn't made it's way to the US! The only time I get it is when I make it at home.
August 8, 2025 at 7:27 PM
I guess the answer to that is “technically, yes.”
August 5, 2025 at 9:55 PM
that's so cool - I love contraptions that are just there to show that we can do something!
July 2, 2025 at 2:52 PM
No shame in appreciating bona fide nerd humor 😉
July 1, 2025 at 8:07 PM
Fact.
April 24, 2025 at 3:20 AM
This got me thinking: Should MCP itself formally distinguish between request vs response context?

It could let LLMs be more intelligent about when to pull extra info. 🤔

[6/6]
April 21, 2025 at 6:57 PM
I built a demo agent for hotel booking. My setup:

Inject request context into the prompt (user prefs, budget, pulled from account)

Fetch response context live using MCP tools (available hotels that match search params)

Result: the agent felt way smarter.

[5/N]
April 21, 2025 at 6:56 PM
Back when we only had prompts, you could frame the task (request context).

Today, tools like MCP change the game. But should you use them?

[4/N]
April 21, 2025 at 6:55 PM
Example: a hotel booking agent 🛌

Request context: "Book a hotel in Barcelona on April 28 under $400"

Response context: A list of hotels available in Barcelona that day, within budget.

[3/N]
April 21, 2025 at 6:55 PM
⚖️ You need to balance two types of context:

Request Context = frames the task

Response Context = info needed to complete it

[2/N]
April 21, 2025 at 6:54 PM
This is really neat, thanks for sharing. Little performance hacks like this require understanding how things work underneath the hood, and tend to have the most impact on overall performance!

Would love to know other similar tips you have.
February 4, 2025 at 6:57 PM