---
title: "Discussion on \"A clean connector does not make a reliable agent\" | Hashnode"
description: "Discussion on \"A clean connector does not make a reliable agent\". Connector correctness and agent behaviour are separate problems. Most teams only test the first one."
url: "https://hashnode.com/posts/mcp-connector-versus-agent/6a66db68e4a9798c2a2c0368"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A clean connector does not make a reliable agent](https://blog.vamsiannamreddy.com/mcp-connector-versus-agent?utm_source=hashnode&utm_medium=feed)

Connector correctness and agent behaviour are separate problems. Most teams only test the first one.

Jul 27 · 2 min read · blog.vamsiannamreddy.com  
Updated 5d ago  
Read the article

-   [#mcp](https://hashnode.com/tag/mcp)
-   [#agents](https://hashnode.com/tag/agents)
-   [#ai-safety](https://hashnode.com/tag/ai-safety)
-   [#evaluation](https://hashnode.com/tag/evaluation)
-   [#production-ai](https://hashnode.com/tag/production-ai)

## Written by

[Vamsi Krishna](https://hashnode.com/@vamsikrishna981)

@vamsikrishna981 · Hyderabad, India

  
[View profile](https://hashnode.com/@vamsikrishna981)

Building production-ready AI systems and sharing practical field notes on LLMs, RAG, agents, evaluation, and governance.

I’m Vamsi, a builder focused on production AI systems. I write Production AI Field Notes to break down the architecture behind reliable LLM apps, RAG, agents, multi-agent workflows, evaluation, observability, safety, and governance. My goal is simple: help builders move beyond impressive AI demos and design systems that can be tested, operated, trusted, and improved in the real world.

## Responses 3

Markdown supported · ⌘↵ to post

[Julian Neagu](https://hashnode.com/@julianneagulab)

[Jul 30](https://hashnode.com/posts/mcp-connector-versus-agent/6a66db68e4a9798c2a2c0368/comment/6a6b14398a746a1bc7f4e710)

This is a common trap with agents. A working tool call does not mean the agent knows when to stop or what success looks like.

[Vamsi Krishna](https://hashnode.com/@vamsikrishna981)

[Jul 28](https://hashnode.com/posts/mcp-connector-versus-agent/6a66db68e4a9798c2a2c0368/comment/6a6868f7eb007823d717cf5d)

Fair point on the varying arguments, and it breaks the stop condition I wrote. The counter has to key on the error rather than the call, and it has to live in the harness.

[Cai](https://hashnode.com/@cailab)

[Jul 28](https://hashnode.com/posts/mcp-connector-versus-agent/6a66db68e4a9798c2a2c0368/comment/6a6860275a2cca572b9a7ae5)

The distinction between connector-level testing and system-level testing is one I had to learn the hard way too. What pushed it home for me was watching an agent cycle through the same three tools forty times, each time getting the same error, and each time trying a slightly different argument instead of stopping. The connector was flawless. The agent had no budget, no circuit breaker, and no way to say I tried everything reasonable and I cannot do this.

The prompt-based approach you mention is the most seductive trap in the space. It feels like you are adding a control, but what you are really doing is adding a suggestion. The model can override it, forget it, or reinterpret it on the next turn. Code that says if tool\_call\_count > 10, stop and report is not elegant, but it is a control that survives model changes and prompt rewrites.

The test that separates the two is exactly right. Most teams are still running connector-green and calling it agent-ready. The trajectory-based evaluation is harder to build, but it is the only thing that tells you whether the system actually works.
