2 result(s)
The article explains why multiple MCP servers often all register a tool named “search”, causing name collisions when a client aggregates tools from more than one server, and gives short-term and long-term fixes (namespacing, unique IDs, client-side resolution changes, or upstream fixes).
The article addresses a common enterprise problem with AWS Bedrock: unknown consumption of AI tokens. It proposes adding explicit bot/user context to model invocation logs so teams can attribute usage, monitor costs, enforce policies, and investigate behavior. The approach uses structured metadata injected at the application or gateway layer and captured in Bedrock invocation logs and downstream observability systems.