4 ms·

What interactions with internal tools? If you can answer that question then the clankers can help you write a deterministic program for that same interaction an

What interactions with internal tools? If you can answer that question then the clankers can help you write a deterministic program for that same interaction and you only spend the tokens once.

piva00 6d ago
I've been doing this myself but it's been extremely hard to get buy-in from the rest of the org. They keep churning MCPs for deterministic interactions while I have tons of little tools written by clankers, not only for clanker-use but also for my own use when needed. Best of both worlds in my view.
0x696C6961 6d ago
Yeah that's a good idea. Then we should standardize these tools and find an easy way for agents to discover and use them. ... Oh wait
- mjmas 6d ago
  And call it not-closed API or something like that.
- 0x445442 5d ago
  Just tell the clanker to read the api documentation that should already exist. You dont need an MCP server for that.
- jimbokun 5d ago
  Congrats you just invented the Unix shell!
locknitpicker 5d ago
> If you can answer that question then the clankers can help you write a deterministic program for that same interaction and you only spend the tokens once. The MCP is the deterministic program. You need to take a step back and look at the problem you're discussing. What's exactly this MCP thing? It's a protocol to allow agents and coding assistants to access tools, services, and data sources, through a standardized interface. It's the interface for your deterministic program. That's it.
- 8note 5d ago
  they were suggesting that you take the agent out of the run time tool usage
  - locknitpicker 5d ago
    > they were suggesting that you take the agent out of the run time tool usage That only applies if you are talking about a well established recurrent workflow. That's not how MCPs are used to begin with.
  - themgt 5d ago
    It's easier if you started a while back shunning all human labor (including your own) in favor of fully deterministic systems. Reality is deterministic so your company or project logically can be run off a single compiled binary with formal verification of correctness for every possible scenario.
    - jimbokun 5d ago
      Heisenberg begs to differ with your view of reality.
      - shwaj 5d ago
        So does Gödel. Maybe it was a joke? Unclear.
- jimbokun 5d ago
  A protocol is not a program.
Sayrus 5d ago
Retrieving messages from Slack over MCP allows a shared read-only bot account accessible from the web browser and CLI. Setup is automated so users can just ask Claude to read them and do something. Sharing Slack with Claude: - Using the "normal" way, it shares too much, including privates messages. - Using your own token, it doesn't work with Claude.AI or Cowork and requires you to go to slack.com to generate an application, tokens and more. - Using a shared token, now you need context to tell Claude to retrieve it. It still doesn't work for non-Claude Code workflows. Rotation may break currently running workflows.
lanstin 5d ago
Yeah. Like I had Claude code write an upload Slab script, and a few linear integration scripts, now it just runs these to interact with those systems. I had it write a redshift proxy that doesn’t take login creds and is just a logging read only account but it can just write sql to research to its hearts content (some columns hashed on replies) and I don’t need much trust but I get a lot of good analysis and verification done.
jimbokun 5d ago
Yes, having LLMs write deterministic programs is still an under used solution. Less token spend, lower latency, more predictable results compared to having the LLM perform the task directly every time.

What interactions with internal tools? If you can answer that question then the clankers can help you write a deterministic program for that same interaction and you only spend the tokens once.

piva00 6d ago

I've been doing this myself but it's been extremely hard to get buy-in from the rest of the org. They keep churning MCPs for deterministic interactions while I have tons of little tools written by clankers, not only for clanker-use but also for my own use when needed. Best of both worlds in my view.

0x696C6961 6d ago

Yeah that's a good idea. Then we should standardize these tools and find an easy way for agents to discover and use them. ... Oh wait

mjmas 6d ago
And call it not-closed API or something like that.
0x445442 5d ago
Just tell the clanker to read the api documentation that should already exist. You dont need an MCP server for that.
jimbokun 5d ago
Congrats you just invented the Unix shell!

locknitpicker 5d ago

> If you can answer that question then the clankers can help you write a deterministic program for that same interaction and you only spend the tokens once. The MCP is the deterministic program. You need to take a step back and look at the problem you're discussing. What's exactly this MCP thing? It's a protocol to allow agents and coding assistants to access tools, services, and data sources, through a standardized interface. It's the interface for your deterministic program. That's it.

8note 5d ago
they were suggesting that you take the agent out of the run time tool usage
- locknitpicker 5d ago
  > they were suggesting that you take the agent out of the run time tool usage That only applies if you are talking about a well established recurrent workflow. That's not how MCPs are used to begin with.
- themgt 5d ago
  It's easier if you started a while back shunning all human labor (including your own) in favor of fully deterministic systems. Reality is deterministic so your company or project logically can be run off a single compiled binary with formal verification of correctness for every possible scenario.
  - jimbokun 5d ago
    Heisenberg begs to differ with your view of reality.
    - shwaj 5d ago
      So does Gödel. Maybe it was a joke? Unclear.
jimbokun 5d ago
A protocol is not a program.

Sayrus 5d ago

Retrieving messages from Slack over MCP allows a shared read-only bot account accessible from the web browser and CLI. Setup is automated so users can just ask Claude to read them and do something. Sharing Slack with Claude: - Using the "normal" way, it shares too much, including privates messages. - Using your own token, it doesn't work with Claude.AI or Cowork and requires you to go to slack.com to generate an application, tokens and more. - Using a shared token, now you need context to tell Claude to retrieve it. It still doesn't work for non-Claude Code workflows. Rotation may break currently running workflows.

lanstin 5d ago

Yeah. Like I had Claude code write an upload Slab script, and a few linear integration scripts, now it just runs these to interact with those systems. I had it write a redshift proxy that doesn’t take login creds and is just a logging read only account but it can just write sql to research to its hearts content (some columns hashed on replies) and I don’t need much trust but I get a lot of good analysis and verification done.

jimbokun 5d ago

Yes, having LLMs write deterministic programs is still an under used solution. Less token spend, lower latency, more predictable results compared to having the LLM perform the task directly every time.