I'm not exactly disagreeing, its just that I don't think that's a criticism of MCP for tool calls.
You need a way to expose tools to LLM, even for what you're talking about. The LLM can't write code without access to code writing tools.
MCP is a protocol for exposing tools to an LLM agent in an extensible way.
If you didn't have MCP for this, the alternative wouldn't be a python script. It would be some other tool calling protocol.
Maybe a good criticism is that the protocol doesn't have a defined mechanism for piping tool calls together. It be nice to define as part of the protocol a standard way for the model to say call tool1 and then pass output.foo as input.bar of tool2.
I feel that can probably be an eventual extension.
As an advanced user of coding agents that you let run locally or have sandboxed yourself, you might get more power and mileage by having it implement scripts and execute them, or use bash/curl and so on, to say access the Google Drive standard APIs for whatever you want to do, than to use the Google Drive MCP. I 100% agree. But that's not adequate for all users, and it's not really an alternative to supporting custom tools in an agent.
You need a way to expose tools to LLM, even for what you're talking about. The LLM can't write code without access to code writing tools.
MCP is a protocol for exposing tools to an LLM agent in an extensible way.
If you didn't have MCP for this, the alternative wouldn't be a python script. It would be some other tool calling protocol.
Maybe a good criticism is that the protocol doesn't have a defined mechanism for piping tool calls together. It be nice to define as part of the protocol a standard way for the model to say call tool1 and then pass output.foo as input.bar of tool2.
I feel that can probably be an eventual extension.
As an advanced user of coding agents that you let run locally or have sandboxed yourself, you might get more power and mileage by having it implement scripts and execute them, or use bash/curl and so on, to say access the Google Drive standard APIs for whatever you want to do, than to use the Google Drive MCP. I 100% agree. But that's not adequate for all users, and it's not really an alternative to supporting custom tools in an agent.